Beam failure and consistent listen before talk failure recovery

ABSTRACT

A wireless device receives message(s) comprising: first configuration parameters for beam failure recovery; and second configuration parameters for LBT failure recovery. The wireless device initiates, based on the first configuration parameters and in response to detecting a beam failure on a primary cell, a first random access process on a first BWP of the primary cell for beam failure recovery. The wireless device triggers, based on the second configuration parameters, consistent LBT failure for the primary cell. The wireless device stops the first random access process, for the beam failure recovery, based on the triggering the consistent LBT failure. The wireless device switches from the first BWP of the primary cell to a second BWP of the primary cell as an active BWP of the primary cell. The wireless device initiates a second random access process on the second BWP of the primary cell.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/945,154, filed Dec. 7, 2019, which is hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A and FIG. 1B show examples of mobile communications systems inaccordance with several of various embodiments of the presentdisclosure.

FIG. 2A and FIG. 2B show examples of user plane and control planeprotocol layers in accordance with several of various embodiments of thepresent disclosure.

FIG. 3 shows example functions and services offered by protocol layersin a user plane protocol stack in accordance with several of variousembodiments of the present disclosure.

FIG. 4 shows example flow of packets through the protocol layers inaccordance with several of various embodiments of the presentdisclosure.

FIG. 5A shows example mapping of channels between layers of the protocolstack and different physical signals in downlink in accordance withseveral of various embodiments of the present disclosure.

FIG. 5B shows example mapping of channels between layers of the protocolstack and different physical signals in uplink in accordance withseveral of various embodiments of the present disclosure.

FIG. 6 shows example physical layer processes for signal transmission inaccordance with several of various embodiments of the presentdisclosure.

FIG. 7 shows examples of RRC states and RRC state transitions inaccordance with several of various embodiments of the presentdisclosure.

FIG. 8 shows an example time domain transmission structure in NR bygrouping OFDM symbols into slots, subframes and frames in accordancewith several of various embodiments of the present disclosure.

FIG. 9 shows an example of time-frequency resource grid in accordancewith several of various embodiments of the present disclosure.

FIG. 10 shows example adaptation and switching of bandwidth parts inaccordance with several of various embodiments of the presentdisclosure.

FIG. 11A shows example arrangements of carriers in carrier aggregationin accordance with several of various embodiments of the presentdisclosure.

FIG. 11B shows examples of uplink control channel groups in accordancewith several of various embodiments of the present disclosure.

FIG. 12A, FIG. 12B and FIG. 12C show example random access processes inaccordance with several of various embodiments of the presentdisclosure.

FIG. 13A shows example time and frequency structure of SSBs and theirassociations with beams in accordance with several of variousembodiments of the present disclosure.

FIG. 13B shows example time and frequency structure of CSI-RSs and theirassociation with beams in accordance with several of various embodimentsof the present disclosure.

FIG. 14A, FIG. 14B and FIG. 14C show example beam management processesin accordance with several of various embodiments of the presentdisclosure.

FIG. 15 shows example components of a wireless device and a base stationthat are in communication via an air interface in accordance withseveral of various embodiments of the present disclosure.

FIG. 16 shows example channel access parameters for listen before talkin accordance with several of various embodiments of the presentdisclosure.

FIG. 17 shows an example LBT failure indication in accordance withseveral of various embodiments of the present disclosure.

FIG. 18 shows scheduling request transmission for consistent LBTfailures recovery in accordance with several of various embodiments ofthe present disclosure.

FIG. 19 shows example scheduling request and random access processes forconsistent LBT failures recovery in accordance with several of variousembodiments of the present disclosure.

FIG. 20 shows example random access processes for consistent LBTfailures recovery in accordance with several of various embodiments ofthe present disclosure.

FIG. 21 shows scheduling request transmission for beam failure recoveryin accordance with several of various embodiments of the presentdisclosure.

FIG. 22 shows example scheduling request and random access processes forbeam failure recovery in accordance with several of various embodimentsof the present disclosure.

FIG. 23 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 24 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 25 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 26 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 27 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 28 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 29 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 30 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 31 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 32 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 33 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 34 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 35 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 36 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 37 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 38 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 39 shows an example process in accordance with several of variousembodiments of the present disclosure.

FIG. 40 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 41 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 42 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 43 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 44 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 45 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 46 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 47 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

DETAILED DESCRIPTION

The exemplary embodiments of the disclosed technology enable operationof a wireless device and/or one or more base stations in unlicensed orshared spectrum and/or using beamforming. The exemplary disclosedembodiments may be implemented in the technical field of wirelesscommunication systems. More particularly, the embodiment of thedisclosed technology may relate to beam failure and consistentlisten-before-talk (LBT) failure recovery.

The devices and/or nodes of the mobile communications system disclosedherein may be implemented based on various technologies and/or variousreleases/versions/amendments of a technology. The various technologiesinclude various releases of long-term evolution (LTE) technologies,various releases of 5G new radio (NR) technologies, various wirelesslocal area networks technologies and/or a combination thereof and/oralike. For example, a base station may support a given technology andmay communicate with wireless devices with different characteristics.The wireless devices may have different categories that define theircapabilities in terms of supporting various features. The wirelessdevice with the same category may have different capabilities. Thewireless devices may support various technologies such as variousreleases of LTE technologies, various releases of 5G NR technologiesand/or a combination thereof and/or alike. At least some of the wirelessdevices in the mobile communications system of the present disclosuremay be stationary or almost stationary. In this disclosure, the terms“mobile communications system” and “wireless communications system” maybe used interchangeably.

FIG. 1A shows an example of a mobile communications system 100 inaccordance with several of various embodiments of the presentdisclosure. The mobile communications system 100 may be, for example,run by a mobile network operator (MNO) or a mobile virtual networkoperator (MVNO). The mobile communications system 100 may be a publicland mobile network (PLMN) run by a network operator providing a varietyof service including voice, data, short messaging service (SMS),multimedia messaging service (MMS), emergency calls, etc. The mobilecommunications system 100 includes a core network (CN) 106, a radioaccess network (RAN) 104 and at least one wireless device 102.

The CN 106 connects the RAN 104 to one or more external networks (e.g.,one or more data networks such as the Internet) and is responsible forfunctions such as authentication, charging and end-to-end connectionestablishment. Several radio access technologies (RATs) may be served bythe same CN 106.

The RAN 104 may implement a RAT and may operate between the at least onewireless device 102 and the CN 106. The RAN 104 may handle radio relatedfunctionalities such as scheduling, radio resource control, modulationand coding, multi-antenna transmissions and retransmission protocols.The wireless device and the RAN may share a portion of the radiospectrum by separating transmissions from the wireless device to the RANand the transmissions from the RAN to the wireless device. The directionof the transmissions from the wireless device to the RAN is known as theuplink and the direction of the transmissions from the RAN to thewireless device is known as the downlink. The separation of uplink anddownlink transmissions may be achieved by employing a duplexingtechnique. Example duplexing techniques include frequency divisionduplexing (FDD), time division duplexing (TDD) or a combination of FDDand TDD.

In this disclosure, the term wireless device may refer to a device thatcommunicates with a network entity or another device using wirelesscommunication techniques. The wireless device may be a mobile device ora non-mobile (e.g., fixed) device. Examples of the wireless deviceinclude cellular phone, smart phone, tablet, laptop computer, wearabledevice (e.g., smart watch, smart shoe, fitness trackers, smart clothing,etc.), wireless sensor, wireless meter, extended reality (XR) devicesincluding augmented reality (AR) and virtual reality (VR) devices,Internet of Things (IoT) device, vehicle to vehicle communicationsdevice, road-side units (RSU), automobile, relay node or any combinationthereof. In some examples, the wireless device (e.g., a smart phone,tablet, etc.) may have an interface (e.g., a graphical user interface(GUI)) for configuration by an end user. In some examples, the wirelessdevice (e.g., a wireless sensor device, etc.) may not have an interfacefor configuration by an end user. The wireless device may be referred toas a user equipment (UE), a mobile station (MS), a subscriber unit, ahandset, an access terminal, a user terminal, a wireless transmit andreceive unit (WTRU) and/or other terminology.

The at least one wireless device may communicate with at least one basestation in the RAN 104. In this disclosure, the term base station mayencompass terminologies associated with various RATs. For example, abase station may be referred to as a Node B in a 3G cellular system suchas Universal Mobile Telecommunication Systems (UMTS), an evolved Node B(eNB) in a 4G cellular system such as evolved universal terrestrialradio access (E-UTRA), a next generation eNB (ng-eNB), a Next GenerationNode B (gNB) in NR and/or a 5G system, an access point (AP) in Wi-Fiand/or other wireless local area networks. A base station may bereferred to as a remote radio head (RRH), a baseband unit (BBU) inconnection with one or more RRHs, a repeater or relay for coverageextension and/or any combination thereof. In some examples, all protocollayers of a base station may be implemented in one unit. In someexample, some of the protocol layers (e.g., upper layers) of the basestation may be implemented in a first unit (e.g., a central unit (CU))and some other protocol layer (e.g., lower layers) may be implemented inone or more second units (e.g., distributed units (DUs)).

A base station in the RAN 104 includes one or more antennas tocommunicate with the at least one wireless device. The base station maycommunicate with the at least one wireless device using radio frequency(RF) transmissions and receptions via RF transceivers. The base stationantennas may control one or more cells (or sectors). The size and/orradio coverage area of a cell may depend on the range that transmissionsby a wireless device can be successfully received by the base stationwhen the wireless device transmits using the RF frequency of the cell.The base station may be associated with cells of various sizes. At agiven location, the wireless device may be in coverage area of a firstcell of the base station and may not be in coverage area of a secondcell of the base station depending on the sizes of the first cell andthe second cell.

A base station in the RAN 104 may have various implementations. Forexample, a base station may be implemented by connecting a BBU (or a BBUpool) coupled to one or more RRHs and/or one or more relay nodes toextend the cell coverage. The BBU pool may be located at a centralizedsite like a cloud or data center. The BBU pool may be connected to aplurality of RRHs that control a plurality of cells. The combination ofBBU with the one or more RRHs may be referred to as a centralized orcloud RAN (C-RAN) architecture. In some implementations, the BBUfunctions may be implemented on virtual machines (VMs) on servers at acentralized location. This architecture may be referred to as virtualRAN (vRAN). All, most or a portion of the protocol layer functions(e.g., all or portions of physical layer, medium access control (MAC)layer and/or higher layers) may be implemented at the BBU pool and theprocessed data may be transmitted to the RRHs for further processingand/or RF transmission. The links between the BBU pool and the RRHs maybe referred to as fronthaul.

In some deployment scenarios, the RAN 104 may include macrocell basestations with high transmission power levels and large coverage areas.In other deployment scenarios, the RAN 104 may include base stationsthat employ different transmission power levels and/or have cells withdifferent coverage areas. For example, some base station may bemacrocell base stations with high transmission powers and/or largecoverage areas and other base station may be small cell base stationswith comparatively smaller transmission powers and/or coverage areas. Insome deployment scenarios, a small cell base station may have coveragethat is within or has overlap with coverage area of a macrocell basestation. A wireless device may communicate with the macrocell basestation while within the coverage area of the macrocell base station.For additional capacity, the wireless device may communicate with boththe macrocell base station and the small cell base station while in theoverlapped coverage area of the macrocell base station and the smallcell base station. Depending on their coverage areas, a small cell basestation may be referred to as a microcell base station, a picocell basestation, a femtocell base station or a home base station.

Different standard development organizations (SDOs) have specified, ormay specify in future, mobile communications systems that have similarcharacteristics as the mobile communications system 100 of FIG. 1A. Forexample, the Third-Generation Partnership Project (3GPP) is a group ofSDOs that provides specifications that define 3GPP technologies formobile communications systems that are akin to the mobile communicationssystem 100. The 3GPP has developed specifications for third generation(3G) mobile networks, fourth generation (4G) mobile networks and fifthgeneration (5G) mobile networks. The 3G, 4G and 5G networks are alsoknown as Universal Mobile Telecommunications System (UMTS), Long TermEvolution (LTE) and 5G system (5GS), respectively. In this disclosure,embodiments are described with respect to the RAN implemented in a 3GPP5G mobile network that is also referred to as next generation RAN(NG-RAN). The embodiments may also be implemented in other mobilecommunications systems such as 3G or 4G mobile networks or mobilenetworks that may be standardized in future such as sixth generation(6G) mobile networks or mobile networks that are implemented bystandards bodies other than 3GPP. The NG-RAN may be based on a new RATknown as new radio (NR) and/or other radio access technologies such asLTE and/or non-3GPP RATs.

FIG. 1B shows an example of a mobile communications system 110 inaccordance with several of various embodiments of the presentdisclosure. The mobile communications system 110 of FIG. 1B is anexample of a 5G mobile network and includes a 5G CN (5G-CN) 130, anNG-RAN 120 and UEs (collectively 112 and individually UE 112A and UE112B). The 5G-CN 130, the NG-RAN 120 and the UEs 112 of FIG. 1B operatesubstantially alike the CN 106, the RAN 104 and the at least onewireless device 102, respectively, as described for FIG. 1A.

The 5G-CN 130 of FIG. 1B connects the NG-RAN 120 to one or more externalnetworks (e.g., one or more data networks such as the Internet) and isresponsible for functions such as authentication, charging andend-to-end connection establishment. The 5G-CN has new enhancementscompared to previous generations of CNs (e.g., evolved packet core (EPC)in the 4G networks) including service-based architecture, support fornetwork slicing and control plane/user plane split. The service-basedarchitecture of the 5G-CN provides a modular framework based on serviceand functionalities provided by the core network wherein a set ofnetwork functions are connected via service-based interfaces. Thenetwork slicing enables multiplexing of independent logical networks(e.g., network slices) on the same physical network infrastructure. Forexample, a network slice may be for mobile broadband applications withfull mobility support and a different network slice may be fornon-mobile latency-critical applications such as industry automation.The control plane/user plane split enables independent scaling of thecontrol plane and the user plane. For example, the control planecapacity may be increased without affecting the user plane of thenetwork.

The 5G-CN 130 of FIG. 1B includes an access and mobility managementfunction (AMF) 132 and a user plane function (UPF) 134. The AMF 132 maysupport termination of non-access stratum (NAS) signaling, NAS signalingsecurity such as ciphering and integrity protection, inter-3GPP accessnetwork mobility, registration management, connection management,mobility management, access authentication and authorization andsecurity context management. The NAS is a functional layer between a UEand the CN and the access stratum (AS) is a functional layer between theUE and the RAN. The UPF 134 may serve as an interconnect point betweenthe NG-RAN and an external data network. The UPF may support packetrouting and forwarding, packet inspection and Quality of Service (QoS)handling and packet filtering. The UPF may further act as a ProtocolData Unit (PDU) session anchor point for mobility within and betweenRATs.

The 5G-CN 130 may include additional network functions (not shown inFIG. 1B) such as one or more Session Management Functions (SMFs), aPolicy Control Function (PCF), a Network Exposure Function (NEF), aUnified Data Management (UDM), an Application Function (AF), and/or anAuthentication Server Function (AUSF). These network functions alongwith the AMF 132 and UPF 134 enable a service-based architecture for the5G-CN.

The NG-RAN 120 may operate between the UEs 112 and the 5G-CN 130 and mayimplement one or more RATs. The NG-RAN 120 may include one or more gNBs(e.g., gNB 122A or gNB 122B or collectively gNBs 122) and/or one or moreng-eNBs (e.g., ng-eNB 124A or ng-eNB 124B or collectively ng-eNBs 124).The general terminology for gNBs 122 and/or an ng-eNBs 124 is a basestation and may be used interchangeably in this disclosure. The gNBs 122and the ng-eNBs 124 may include one or more antennas to communicate withthe UEs 112. The one or more antennas of the gNBs 122 or ng-eNBs 124 maycontrol one or more cells (or sectors) that provide radio coverage forthe UEs 112.

A gNB and/or an ng-eNB of FIG. 1B may be connected to the 5G-CN 130using an NG interface. A gNB and/or an ng-eNB may be connected withother gNBs and/or ng-eNBs using an Xn interface. The NG or the Xninterfaces are logical connections that may be established using anunderlying transport network. The interface between a UE and a gNB orbetween a UE and an ng-eNBs may be referred to as the Uu interface. Aninterface (e.g., Uu, NG or Xn) may be established by using a protocolstack that enables data and control signaling exchange between entitiesin the mobile communications system of FIG. 1B. When a protocol stack isused for transmission of user data, the protocol stack may be referredto as user plane protocol stack. When a protocol stack is used fortransmission of control signaling, the protocol stack may be referred toas control plane protocol stack. Some protocol layer may be used in bothof the user plane protocol stack and the control plane protocol stackwhile other protocol layers may be specific to the user plane or controlplane.

The NG interface of FIG. 1B may include an NG-User plane (NG-U)interface between a gNB and the UPF 134 (or an ng-eNB and the UPF 134)and an NG-Control plane (NG-C) interface between a gNB and the AMF 132(or an ng-eNB and the AMF 132). The NG-U interface may providenon-guaranteed delivery of user plane PDUs between a gNB and the UPF oran ng-eNB and the UPF. The NG-C interface may provide services such asNG interface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer and/or warning message transmission.

The UEs 112 and a gNB may be connected using the Uu interface and usingthe NR user plane and control plane protocol stack. The UEs 112 and anng-eNB may be connected using the Uu interface using the LTE user planeand control plane protocol stack.

In the example mobile communications system of FIG. 1B, a 5G-CN isconnected to a RAN comprised of 4G LTE and/or 5G NR RATs. In otherexample mobile communications systems, a RAN based on the 5G NR RAT maybe connected to a 4G CN (e.g., EPC). For example, earlier releases of 5Gstandards may support a non-standalone mode of operation where a NRbased RAN is connected to the 4G EPC. In an example non-standalone mode,a UE may be connected to both a 5G NR gNB and a 4G LTE eNB (e.g., ang-eNB) and the control plane functionalities (such as initial access,paging and mobility) may be provided through the 4G LTE eNB. In astandalone of operation, the 5G NR gNB is connected to a 5G-CN and theuser plane and the control plane functionalities are provided by the 5GNR gNB.

FIG. 2A shows an example of the protocol stack for the user plan of anNR Uu interface in accordance with several of various embodiments of thepresent disclosure. The user plane protocol stack comprises fiveprotocol layers that terminate at the UE 200 and the gNB 210. The fiveprotocol layers, as shown in FIG. 2A, include physical (PHY) layerreferred to as PHY 201 at the UE 200 and PHY 211 at the gNB 210, mediumaccess control (MAC) layer referred to as MAC 202 at the UE 200 and MAC212 at the gNB 210, radio link control (RLC) layer referred to as RLC203 at the UE 200 and RLC 213 at the gNB 210, packet data convergenceprotocol (PDCP) layer referred to as PDCP 204 at the UE 200 and PDCP 214at the gNB 210, and service data application protocol (SDAP) layerreferred to as SDAP 205 at the UE 200 and SDAP 215 at the gNB 210. ThePHY layer, also known as layer 1 (L1), offers transport services tohigher layers. The other four layers of the protocol stack (MAC, RLC,PDCP and SDAP) are collectively known as layer 2 (L2).

FIG. 2B shows an example of the protocol stack for the control plan ofan NR Uu interface in accordance with several of various embodiments ofthe present disclosure. Some of the protocol layers (PHY, MAC, RLC andPDCP) are common between the user plane protocol stack shown in FIG. 2Aand the control plan protocol stack. The control plane protocol stackalso includes the RRC layer, referred to RRC 206 at the UE 200 and RRC216 at the gNB 210, that also terminates at the UE 200 and the gNB 210.In addition, the control plane protocol stack includes the NAS layerthat terminates at the UE 200 and the AMF 220. In FIG. 2B, the NAS layeris referred to as NAS 207 at the UE 200 and NAS 227 at the AMF 220.

FIG. 3 shows example functions and services offered to other layers by alayer in the NR user plane protocol stack of FIG. 2A in accordance withseveral of various embodiments of the present disclosure. For example,the SDAP layer of FIG. 3 (shown in FIG. 2A as SDAP 205 at the UE sideand SDAP 215 at the gNB side) may perform mapping and de-mapping of QoSflows to data radio bearers. The mapping and de-mapping may be based onQoS (e.g., delay, throughput, jitter, error rate, etc.) associated witha QoS flow. A QoS flow may be a QoS differentiation granularity for aPDU session which is a logical connection between a UE 200 and a datanetwork. A PDU session may contain one or more QoS flows. The functionsand services of the SDAP layer include mapping and de-mapping betweenone or more QoS flows and one or more data radio bearers. The SDAP layermay also mark the uplink and/or downlink packets with a QoS flow ID(QFI).

The PDCP layer of FIG. 3 (shown in FIG. 2A as PDCP 204 at the UE sideand PDCP 214 at the gNB side) may perform header compression anddecompression (e.g., using Robust Header Compression (ROHC) protocol) toreduce the protocol header overhead, ciphering and deciphering andintegrity protection and verification to enhance the security over theair interface, reordering and in-order delivery of packets anddiscarding of duplicate packets. A UE may be configured with one PDCPentity per bearer.

In an example scenario not shown in FIG. 3, a UE may be configured withdual connectivity and may connect to two different cell groups providedby two different base stations. For example, a base station of the twobase stations may be referred to as a master base station and a cellgroup provided by the master base station may be referred to as a mastercell group (MCG). The other base station of the two base stations may bereferred to as a secondary base station and the cell group provided bythe secondary base station may be referred to as a secondary cell group(SCG). A bearer may be configured for the UE as a split bearer that maybe handled by the two different cell groups. The PDCP layer may performrouting of packets corresponding to a split bearer to and/or from RLCchannels associated with the cell groups.

In an example scenario not shown in FIG. 3, a bearer of the UE may beconfigured (e.g., with control signaling) with PDCP packet duplication.A bearer configured with PDCP duplication may be mapped to a pluralityof RLC channels each corresponding to different one or more cells. ThePDCP layer may duplicate packets of the bearer configured with PDCPduplication and the duplicated packets may be mapped to the differentRLC channels. With PDCP packet duplication, the likelihood of correctreception of packets increases thereby enabling higher reliability.

The RLC layer of FIG. 3 (shown in FIG. 2A as RLC 203 at the UE side andRLC 213 at the gNB side) provides service to upper layers in the form ofRLC channels. The RLC layer may include three transmission modes:transparent mode (TM), Unacknowledged mode (UM) and Acknowledged mode(AM). The RLC layer may perform error correction through automaticrepeat request (ARQ) for the AM transmission mode, segmentation of RLCservice data units (SDUs) for the AM and UM transmission modes andre-segmentation of RLC SDUs for AM transmission mode, duplicatedetection for the AM transmission mode, RLC SDU discard for the AM andUM transmission modes, etc. The UE may be configured with one RLC entityper RLC channel.

The MAC layer of FIG. 3 (shown in FIG. 2A as MAC 202 at the UE side andMAC 212 at the gNB side) provides services to the RLC layer in form oflogical channels. The MAC layer may perform mapping between logicalchannels and transport channels, multiplexing/demultiplexing of MAC SDUsbelonging to one or more logical channels into/from transport blocks(TBs) delivered to/from the physical layer on transport channels,reporting of scheduling information, error correction through hybridautomatic repeat request (HARQ), priority handling between UEs by meansof dynamic scheduling, priority handling between logical channels of oneUE by means of logical channel prioritization and/or padding. In case ofcarrier aggregation, a MAC entity may comprise one HARQ entity per cell.A MAC entity may support multiple numerologies, transmission timings andcells. The control signaling may configure logical channels with mappingrestrictions. The mapping restrictions in logical channel prioritizationmay control the numerology(ies), cell(s), and/or transmissiontiming(s)/duration(s) that a logical channel may use.

The PHY layer of FIG. 3 (shown in FIG. 2A as PHY 201 at the UE side andPHY 211 at the gNB side) provides transport services to the MAC layer inform of transport channels. The physical layer may handlecoding/decoding, HARQ soft combining, rate matching of a coded transportchannel to physical channels, mapping of coded transport channels tophysical channels, modulation and demodulation of physical channels,frequency and time synchronization, radio characteristics measurementsand indication to higher layers, RF processing, and mapping to antennasand radio resources.

FIG. 4 shows example processing of packets at different protocol layersin accordance with several of various embodiments of the presentdisclosure. In this example, three Internet Protocol (IP) packets thatare processed by the different layers of the NR protocol stack. The termSDU shown in FIG. 4 is the data unit that is entered from/to a higherlayer. In contrast, a protocol data unit (PDU) is the data unit that isentered to/from a lower layer. The flow of packets in FIG. 4 is fordownlink. An uplink data flow through layers of the NR protocol stack issimilar to FIG. 4. In this example, the two leftmost IP packets aremapped by the SDAP layer (shown as SDAP 205 and SDAP 215 in FIG. 2A) toradio bearer 402 and the rightmost packet is mapped by the SDAP layer tothe radio bearer 404. The SDAP layer adds SDAP headers to the IP packetswhich are entered into the PDCP layer as PDCP SDUs. The PDCP layer isshown as PDCP 204 and PDCP 214 in FIG. 2A. The PDCP layer adds the PDCPheaders to the PDCP SDUs which are entered into the RLC layer as RLCSDUs. The RLC layer is shown as RLC 203 and RLC 213 in FIG. 2A. An RLCSDU may be segmented at the RLC layer. The RLC layer adds RLC headers tothe RLC SDUs after segmentation (if segmented) which are entered intothe MAC layer as MAC SDUs. The MAC layer adds the MAC headers to the MACSDUs and multiplexes one or more MAC SDUs to form a PHY SDU (alsoreferred to as a transport block (TB) or a MAC PDU).

In FIG. 4, the MAC SDUs are multiplexed to form a transport block. TheMAC layer may multiplex one or more MAC control elements (MAC CEs) withzero or more MAC SDUs to form a transport block. The MAC CEs may also bereferred to as MAC commands or MAC layer control signaling and may beused for in-band control signaling. The MAC CEs may be transmitted by abase station to a UE (e.g., downlink MAC CEs) or by a UE to a basestation (e.g., uplink MAC CEs). The MAC CEs may be used for transmissionof information useful by a gNB for scheduling (e.g., buffer statusreport (BSR) or power headroom report (PHR)), activation/deactivation ofone or more cells, activation/deactivation of configured radio resourcesfor or one or more processes, activation/deactivation of one or moreprocesses, indication of parameters used in one or more processes, etc.

FIG. 5A and FIG. 5B show example mapping between logical channels,transport channels and physical channels for downlink and uplink,respectively in accordance with several of various embodiments of thepresent disclosure. As discussed before, the MAC layer provides servicesto higher layer in the form of logical channels. A logical channel maybe classified as a control channel, if used for transmission of controland/or configuration information, or a traffic channel if used fortransmission of user data. Example logical channels in NR includeBroadcast Control Channel (BCCH) used for transmission of broadcastsystem control information, Paging Control Channel (PCCH) used forcarrying paging messages for wireless devices with unknown locations,Common Control Channel (CCCH) used for transmission of controlinformation between UEs and network and for UEs that have no RRCconnection with the network, Dedicated Control Channel (DCCH) which is apoint-to-point bi-directional channel for transmission of dedicatedcontrol information between a UE that has an RRC connection and thenetwork and Dedicated Traffic Channel (DTCH) which is point-to-pointchannel, dedicated to one UE, for the transfer of user information andmay exist in both uplink and downlink.

As discussed before, the PHY layer provides services to the MAC layerand higher layers in the form of transport channels. Example transportchannels in NR include Broadcast Channel (BCH) used for transmission ofpart of the BCCH referred to as master information block (MIB), DownlinkShared Channel (DL-SCH) used for transmission of data (e.g., from DTCHin downlink) and various control information (e.g., from DCCH and CCCHin downlink and part of the BCCH that is not mapped to the BCH), UplinkShared Channel (UL-SCH) used for transmission of uplink data (e.g., fromDTCH in uplink) and control information (e.g., from CCCH and DCCH inuplink) and Paging Channel (PCH) used for transmission of paginginformation from the PCCH. In addition, Random Access Channel (RACH) isa transport channel used for transmission of random access preambles.The RACH does not carry a transport block. Data on a transport channel(except RACH) may be organized in transport blocks, wherein One or moretransport blocks may be transmitted in a transmission time interval(TTI).

The PHY layer may map the transport channels to physical channels. Aphysical channel may correspond to time-frequency resources that areused for transmission of information from one or more transportchannels. In addition to mapping transport channels to physicalchannels, the physical layer may generate control information (e.g.,downlink control information (DCI) or uplink control information (UCI))that may be carried by the physical channels. Example DCI includescheduling information (e.g., downlink assignments and uplink grants),request for channel state information report, power control command,etc. Example UCI include HARQ feedback indicating correct or incorrectreception of downlink transport blocks, channel state informationreport, scheduling request, etc. Example physical channels in NR includea Physical Broadcast Channel (PBCH) for carrying information from theBCH, a Physical Downlink Shared Channel (PDSCH) for carrying informationform the PCH and the DL-SCH, a Physical Downlink Control Channel (PDCCH)for carrying DCI, a Physical Uplink Shared Channel (PUSCH) for carryinginformation from the UL-SCH and/or UCI, a Physical Uplink ControlChannel (PUCCH) for carrying UCI and Physical Random Access Channel(PRACH) for transmission of RACH (e.g., random access preamble).

The PHY layer may also generate physical signals that are not originatedfrom higher layers. As shown in FIG. 5A, example downlink physicalsignals include Demodulation Reference Signal (DM-RS), Phase TrackingReference Signal (PT-RS), Channel State Information Reference Signal(CSI-RS), Primary Synchronization Signal (PSS) and SecondarySynchronization Signal (SSS). As shown in FIG. 5B, example uplinkphysical signals include DM-RS, PT-RS and sounding reference signal(SRS).

As indicated earlier, some of the protocol layers (PHY, MAC, RLC andPDCP) of the control plane of an NR Uu interface, are common between theuser plane protocol stack (as shown in FIG. 2A) and the control planeprotocol stack (as shown in FIG. 2B). In addition to PHY, MAC, RLC andPDCP, the control plane protocol stack includes the RRC protocol layerand the NAS protocol layer.

The NAS layer, as shown in FIG. 2B, terminates at the UE 200 and the AMF220 entity of the 5G-C 130. The NAS layer is used for core networkrelated functions and signaling including registration, authentication,location update and session management. The NAS layer uses services fromthe AS of the Uu interface to transmit the NAS messages.

The RRC layer, as shown in FIG. 2B, operates between the UE 200 and thegNB 210 (more generally NG-RAN 120) and may provide services andfunctions such as broadcast of system information (SI) related to AS andNAS as well as paging initiated by the 5G-C 130 or NG-RAN 120. Inaddition, the RRC layer is responsible for establishment, maintenanceand release of an RRC connection between the UE 200 and the NG-RAN 120,carrier aggregation configuration (e.g., addition, modification andrelease), dual connectivity configuration (e.g., addition, modificationand release), security related functions, radio bearerconfiguration/maintenance and release, mobility management (e.g.,maintenance and context transfer), UE cell selection and reselection,inter-RAT mobility, QoS management functions, UE measurement reportingand control, radio link failure (RLF) detection and NAS messagetransfer. The RRC layer uses services from PHY, MAC, RLC and PDCP layersto transmit RRC messages using signaling radio bearers (SRBs). The SRBsare mapped to CCCH logical channel during connection establishment andto DCCH logical channel after connection establishment.

FIG. 6 shows example physical layer processes for signal transmission inaccordance with several of various embodiments of the presentdisclosure. Data and/or control streams from MAC layer may beencoded/decoded to offer transport and control services over the radiotransmission link. For example, one or more (e.g., two as shown in FIG.6) transport blocks may be received from the MAC layer for transmissionvia a physical channel (e.g., a physical downlink shared channel or aphysical uplink shared channel). A cyclic redundancy check (CRC) may becalculated and attached to a transport block in the physical layer. TheCRC calculation may be based on one or more cyclic generatorpolynomials. The CRC may be used by the receiver for error detection.Following the transport block CRC attachment, a low-density parity check(LDPC) base graph selection may be performed. In example embodiments,two LDPC base graphs may be used wherein a first LDPC base graph may beoptimized for small transport blocks and a second LDPC base graph may beoptimized for comparatively larger transport blocks.

The transport block may be segmented into code blocks and code block CRCmay be calculated and attached to a code block. A code block may be LDPCcoded and the LDPC coded blocks may be individually rate matched. Thecode blocks may be concatenated to create one or more codewords. Thecontents of a codeword may be scrambled and modulated to generate ablock of complex-valued modulation symbols. The modulation symbols maybe mapped to a plurality of transmission layers (e.g., multiple-inputmultiple-output (MIMO) layers) and the transmission layers may besubject to transform precoding and/or precoding. The precodedcomplex-valued symbols may be mapped to radio resources (e.g., resourceelements). The signal generator block may create a baseband signal andup-convert the baseband signal to a carrier frequency for transmissionvia antenna ports. The signal generator block may employ mixers, filtersand/or other radio frequency (RF) components prior to transmission viathe antennas. The functions and blocks in FIG. 6 are illustrated asexamples and other mechanisms may be implemented in various embodiments.

FIG. 7 shows examples of RRC states and RRC state transitions at a UE inaccordance with several of various embodiments of the presentdisclosure. A UE may be in one of three RRC states: RRC_IDLE 702, RRCINACTIVE 704 and RRC_CONNECTED 706. In RRC_IDLE 702 state, no RRCcontext (e.g., parameters needed for communications between the UE andthe network) may be established for the UE in the RAN. In RRC_IDLE 702state, no data transfer between the UE and the network may take placeand uplink synchronization is not maintained. The wireless device maysleep most of the time and may wake up periodically to receive pagingmessages. The uplink transmission of the UE may be based on a randomaccess process and to enable transition to the RRC_CONNECTED 706 state.The mobility in RRC_IDLE 702 state is through a cell reselectionprocedure where the UE camps on a cell based on one or more criteriaincluding signal strength that is determined based on the UEmeasurements.

In RRC_CONNECTED 706 state, the RRC context is established and both theUE and the RAN have necessary parameters to enable communicationsbetween the UE and the network. In the RRC_CONNECTED 706 state, the UEis configured with an identity known as a Cell Radio Network TemporaryIdentifier (C-RNTI) that is used for signaling purposes (e.g., uplinkand downlink scheduling, etc.) between the UE and the RAN. The wirelessdevice mobility in the RRC_CONNECTED 706 state is managed by the RAN.The wireless device provides neighboring cells and/or current servingcell measurements to the network and the network may make hand overdecisions. Based on the wireless device measurements, the currentserving base station may send a handover request message to aneighboring base station and may send a handover command to the wirelessdevice to handover to a cell of the neighboring base station. Thetransition of the wireless device from the RRC_IDLE 702 state to theRRC_CONNECTED 706 state or from the RRC_CONNECTED 706 state to theRRC_IDLE 702 state may be based on connection establishment andconnection release procedures (shown collectively as connectionestablishment/release 710 in FIG. 7).

To enable a faster transition to the RRC_CONNECTED 706 state (e.g.,compared to transition from RRC_IDLE 702 state to RRC_CONNECTED 706state), an RRC_INACTIVE 704 state is used for an NR UE wherein, the RRCcontext is kept at the UE and the RAN. The transition from theRRC_INACTIVE 704 state to the RRC_CONNECTED 706 state is handled by RANwithout CN signaling. Similar to the RRC_IDLE 702 state, the mobility inRRC_INACTIVE 704 state is based on a cell reselection procedure withoutinvolvement from the network. The transition of the wireless device fromthe RRC_INACTIVE 704 state to the RRC_CONNECTED 706 state or from theRRC_CONNECTED 706 state to the RRC_INACTIVE 704 state may be based onconnection resume and connection inactivation procedures (showncollectively as connection resume/inactivation 712 in FIG. 7). Thetransition of the wireless device from the RRC_INACTIVE 704 state to theRRC_IDLE 702 state may be based on a connection release 714 procedure asshown in FIG. 7.

In NR, Orthogonal Frequency Division Multiplexing (OFDM), also calledcyclic prefix OFDM (CP-OFDM), is the baseline transmission scheme inboth downlink and uplink of NR and the Discrete Fourier Transform (DFT)spread OFDM (DFT-s-OFDM) is a complementary uplink transmission inaddition to the baseline OFDM scheme. OFDM is multi-carrier transmissionscheme wherein the transmission bandwidth may be composed of severalnarrowband sub-carriers. The subcarriers are modulated by the complexvalued OFDM modulation symbols resulting in an OFDM signal. The complexvalued OFDM modulation symbols are obtained by mapping, by a modulationmapper, the input data (e.g., binary digits) to different points of amodulation constellation diagram. The modulation constellation diagramdepends on the modulation scheme. NR may use different types ofmodulation schemes including Binary Phase Shift Keying (BPSK), π/2-BPSK,Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation(16QAM), 64QAM and 256QAM. Different and/or higher order modulationschemes (e.g., M-QAM in general) may be used. An OFDM signal with Nsubcarriers may be generated by processing N subcarriers in parallel forexample by using Inverse Fast Fourier Transform (IFFT) processing. TheOFDM receiver may use FFT processing to recover the transmitted OFDMmodulation symbols. The subcarrier spacing of subcarriers in an OFDMsignal is inversely proportional to an OFDM modulation symbol duration.For example, for a 15 KHz subcarrier spacing, duration of an OFDM signalis nearly 66.7 μs. To enhance the robustness of OFDM transmission intime dispersive channels, a cyclic prefix (CP) may be inserted at thebeginning of an OFDM symbol. For example, the last part of an OFDMsymbol may be copied and inserted at the beginning of an OFDM symbol.The CP insertion enhanced the OFDM transmission scheme by preservingsubcarrier orthogonality in time dispersive channels.

In NR, different numerologies may be used for OFDM transmission. Anumerology of OFDM transmission may indicate a subcarrier spacing and aCP duration for the OFDM transmission. For example, a subcarrier spacingin NR may generally be a multiple of 15 KHz and expressed as Δf=2^(μ)·15KHz (μ=0, 1, 2, . . . ). Example subcarrier spacings used in NR include15 KHz (μ=0), 30 KHz (μ=1), 60 KHz (μ=2), 120 KHz (μ=3) and 240 KHz(μ=4). As discussed before, a duration of OFDM symbol is inverselyproportional to the subcarrier spacing and therefor OFDM symbol durationmay depend on the numerology (e.g. the p value).

FIG. 8 shows an example time domain transmission structure in NR whereinOFDM symbols are grouped into slots, subframes and frames in accordancewith several of various embodiments of the present disclosure. A slot isa group of N_(symb) ^(slot) OFDM symbols, wherein the N_(symb) ^(slot)may have a constant value (e.g., 14). Since different numerologiesresults in different OFDM symbol durations, duration of a slot may alsodepend on the numerology and may be variable. A subframe may have aduration of 1 ms and may be composed of one or more slots, the number ofwhich may depend on the slot duration. The number of slots per subframeis therefore a function of μ and may generally expressed as N_(slot)^(subframe,μ) and the number of symbols per subframe may be expressed asN_(symb) ^(subframe,μ)=N_(symb) ^(slot)N_(slot) ^(subframe,μ). A framemay have a duration of 10 ms and may consist of 10 subframes. The numberof slots per frame may depend on the numerology and therefore may bevariable. The number of slots per frame may generally be expressed asN_(slot) ^(frame,μ).

An antenna port may be defined as a logical entity such that channelcharacteristics over which a symbol on the antenna port is conveyed maybe inferred from the channel characteristics over which another symbolon the same antenna port is conveyed. For example, for DM-RS associatedwith a PDSCH, the channel over which a PDSCH symbol on an antenna portis conveyed may be inferred from the channel over which a DM-RS symbolon the same antenna port is conveyed, for example, if the two symbolsare within the same resource as the scheduled PDSCH and/or in the sameslot and/or in the same precoding resource block group (PRG). Forexample, for DM-RS associated with a PDCCH, the channel over which aPDCCH symbol on an antenna port is conveyed may be inferred from thechannel over which a DM-RS symbol on the same antenna port is conveyedif, for example, the two symbols are within resources for which the UEmay assume the same precoding being used. For example, for DM-RSassociated with a PBCH, the channel over which a PBCH symbol on oneantenna port is conveyed may be inferred from the channel over which aDM-RS symbol on the same antenna port is conveyed if, for example, thetwo symbols are within a SS/PBCH block transmitted within the same slot,and with the same block index. The antenna port may be different from aphysical antenna. An antenna port may be associated with an antenna portnumber and different physical channels may correspond to differentranges of antenna port numbers.

FIG. 9 shows an example of time-frequency resource grid in accordancewith several of various embodiments of the present disclosure. Thenumber of subcarriers in a carrier bandwidth may be based on thenumerology of OFDM transmissions in the carrier. A resource element,corresponding to one symbol duration and one subcarrier, may be thesmallest physical resource in the time-frequency grid. A resourceelement (RE) for antenna port p and subcarrier spacing configuration μmay be uniquely identified by (k,l)_(p,μ) where k is the index of asubcarrier in the frequency domain and l may refer to the symbolposition in the time domain relative to some reference point. A resourceblock may be defined as N_(SC) ^(RB)=12 subcarriers. Since subcarrierspacing depends on the numerology of OFDM transmission, the frequencydomain span of a resource block may be variable and may depend on thenumerology. For example, for a subcarrier spacing of 15 KHz (e.g., μ=0),a resource block may be 180 KHz and for a subcarrier spacing of 30 KHz(e.g., μ=1), a resource block may be 360 KHz.

With large carrier bandwidths defined in NR and due to limitedcapabilities for some UEs (e.g., due to hardware limitations), a UE maynot support an entire carrier bandwidth. Receiving on the full carrierbandwidth may imply high energy consumption. For example, transmittingdownlink control channels on the full downlink carrier bandwidth mayresult in high power consumption for wide carrier bandwidths. NR may usea bandwidth adaptation procedure to dynamically adapt the transmit andreceive bandwidths. The transmit and receive bandwidth of a UE on a cellmay be smaller than the bandwidth of the cell and may be adjusted. Forexample, the width of the transmit and/or receive bandwidth may change(e.g. shrink during period of low activity to save power); the locationof the transmit and/or receive bandwidth may move in the frequencydomain (e.g. to increase scheduling flexibility); and the subcarrierspacing of the transmit or receive bandwidth may change (e.g. to allowdifferent services). A subset of the cell bandwidth may be referred toas a Bandwidth Part (BWP) and bandwidth adaptation may be achieved byconfiguring the UE with one or more BWPs. The base station may configurea UE with a set of downlink BWPs and a set of uplink BWPs. A BWP may becharacterized by a numerology (e.g., subcarrier spacing and cyclicprefix) and a set of consecutive resource blocks in the numerology ofthe BWP. One or more first BWPs of the one or more BWPs of the cell maybe active at a time. An active BWP may be an active downlink BWP or anactive uplink BWP.

FIG. 10 shows an example of bandwidth part adaptation and switching. Inthis example, three BWPs (BWP₁ 1004, BWP₂ 1006 and BWP₃ 1008) areconfigured for a UE on a carrier bandwidth. The BWP₁ is configured witha bandwidth of 40 MHz and a numerology with subcarrier spacing of 15KHz, the BWP₂ is configured with a bandwidth of 10 MHz and a numerologywith subcarrier spacing of 15 KHz and the BWP₃ is configured with abandwidth of 20 MHz and a subcarrier spacing of 60 KHz. The wirelessdevice may switch from a first BWP (e.g., BWP₁) to a second BWP (e.g.,BWP₂). An active BWP of the cell may change from the first BWP to thesecond BWP in response to the BWP switching.

The BWP switching (e.g., BWP switching 1010, BWP switching 1012, BWPswitching 1014, or BWP switching 1016 in FIG. 10) may be based on acommand from the base station. The command may be a DCI comprisingscheduling information for the UE in the second BWP. In case of uplinkBWP switching, the first BWP and the second BWP may be uplink BWPs andthe scheduling information may be an uplink grant for uplinktransmission via the second BWP. In case of downlink BWP switching, thefirst BWP and the second BWP may be downlink BWPs and the schedulinginformation may be a downlink assignment for downlink reception via thesecond BWP.

The BWP switching (e.g., BWP switching 1010, BWP switching 1012, BWPswitching 1014, or BWP switching 1016 in FIG. 10) may be based on anexpiry of a timer. The base station may configure a wireless device witha BWP inactivity timer and the wireless device may switch to a defaultBWP (e.g., default downlink BWP) based on the expiry of the BWPinactivity timer. The expiry of the BWP inactivity timer may be anindication of low activity on the current active downlink BWP. The basestation may configure the wireless device with the default downlink BWP.If the base station does not configure the wireless device with thedefault BWP, the default BWP may be an initial downlink BWP. The initialactive BWP may be the BWP that the wireless device receives schedulinginformation for remaining system information upon transition to anRRC_CONNECTED state.

A wireless device may monitor a downlink control channel of a downlinkBWP. For example, the UE may monitor a set of PDCCH candidates inconfigured monitoring occasions in one or more configured COntrolREsource SETs (CORESETs) according to the corresponding search spaceconfigurations. A search space configuration may define how/where tosearch for PDCCH candidates. For example, the search space configurationparameters may comprise a monitoring periodicity and offset parameterindicating the slots for monitoring the PDCCH candidates. The searchspace configuration parameters may further comprise a parameterindicating a first symbol with a slot within the slots determined formonitoring PDCCH candidates. A search space may be associated with oneor more CORESETs and the search space configuration may indicate one ormore identifiers of the one or more CORESETs. The search spaceconfiguration parameters may further indicate that whether the searchspace is a common search space or a UE-specific search space. A commonsearch space may be monitored by a plurality of wireless devices and aUE-specific search space may be dedicated to a specific UE.

FIG. 11A shows example arrangements of carriers in carrier aggregationin accordance with several of various embodiments of the presentdisclosure. With carrier aggregation, multiple NR component carriers(CCs) may be aggregated. Downlink transmissions to a wireless device maytake place simultaneously on the aggregated downlink CCs resulting inhigher downlink data rates. Uplink transmissions from a wireless devicemay take place simultaneously on the aggregated uplink CCs resulting inhigher uplink data rates. The component carriers in carrier aggregationmay be on the same frequency band (e.g., intra-band carrier aggregation)or on different frequency bands (e.g., inter-band carrier aggregation).The component carriers may also be contiguous or non-contiguous. Thisresults in three possible carrier aggregation scenarios, intra-bandcontiguous CA 1102, intra-band non-contiguous CA 1104 and inter-band CA1106 as shown in FIG. 11A. Depending on the UE capability for carrieraggregation, a UE may transmit and/or receive on multiple carriers orfor a UE that is not capable of carrier aggregation, the UE may transmitand/or receive on one component carrier at a time. In this disclosure,the carrier aggregation is described using the term cell and a carrieraggregation capable UE may transmit and/or receive via multiple cells.

In carrier aggregation, a UE may be configured with multiple cells. Acell of the multiple cells configured for the UE may be referred to as aPrimary Cell (PCell). The PCell may be the first cell that the UE isinitially connected to. One or more other cells configured for the UEmay be referred to as Secondary Cells (SCells). The base station mayconfigure a UE with multiple SCells. The configured SCells may bedeactivated upon configuration and the base station may dynamicallyactivate or deactivate one or more of the configured SCells based ontraffic and/or channel conditions. The base station may activate ordeactivate configured SCells using a SCell Activation/Deactivation MACCE. The SCell Activation/Deactivation MAC CE may comprise a bitmap,wherein each bit in the bitmap may correspond to a SCell and the valueof the bit indicates an activation status or deactivation status of theSCell.

An SCell may also be deactivated in response to expiry of a SCelldeactivation timer of the SCell. The expiry of an SCell deactivationtimer of an SCell may be an indication of low activity (e.g., lowtransmission or reception activity) on the SCell. The base station mayconfigure the SCell with an SCell deactivation timer. The base stationmay not configure an SCell deactivation timer for an SCell that isconfigured with PUCCH (also referred to as a PUCCH SCell). Theconfiguration of the SCell deactivation timer may be per configuredSCell and different SCells may be configured with different SCelldeactivation timer values. The SCell deactivation timer may be restartedbased on one or more criteria including reception of downlink controlinformation on the SCell indicating uplink grant or downlink assignmentfor the SCell or reception of downlink control information on ascheduling cell indicating uplink grant or downlink assignment for theSCell or transmission of a MAC PDU based on a configured uplink grant orreception of a configured downlink assignment.

A PCell for a UE may be an SCell for another UE and a SCell for a UE maybe PCell for another UE. The configuration of PCell may be UE-specific.One or more SCells of the multiple SCells configured for a UE may beconfigured as downlink-only SCells, e.g., may only be used for downlinkreception and may not be used for uplink transmission. In case ofself-scheduling, the base station may transmit signaling for uplinkgrants and/or downlink assignments on the same cell that thecorresponding uplink or downlink transmission takes place. In case ofcross-carrier scheduling, the base station may transmit signaling foruplink grants and/or downlink assignments on a cell different from thecell that the corresponding uplink or downlink transmission takes place.

FIG. 11B shows examples of uplink control channel groups in accordancewith several of various embodiments of the present disclosure. A basestation may configure a UE with multiple PUCCH groups wherein a PUCCHgroup comprises one or more cells. For example, as shown in FIG. 11B,the base station may configure a UE with a primary PUCCH group 1114 anda secondary PUCCH group 1116. The primary PUCCH group may comprise thePCell 1110 and one or more first SCells. First UCI corresponding to thePCell and the one or more first SCells of the primary PUCCH group may betransmitted by the PUCCH of the PCell. The first UCI may be, forexample, HARQ feedback for downlink transmissions via downlink CCs ofthe PCell and the one or more first SCells. The secondary PUCCH groupmay comprise a PUCCH SCell and one or more second SCells. Second UCIcorresponding to the PUCCH SCell and the one or more second SCells ofthe secondary PUCCH group may be transmitted by the PUCCH of the PUCCHSCell. The second UCI may be, for example, HARQ feedback for downlinktransmissions via downlink CCs of the PUCCH SCell and the one or moresecond SCells.

FIG. 12A, FIG. 12B and FIG. 12C show example random access processes inaccordance with several of various embodiments of the presentdisclosure. FIG. 12A shows an example of four step contention-basedrandom access (CBRA) procedure. The four-step CBRA procedure includesexchanging four messages between a UE and a base station. Msg1 may befor transmission (or retransmission) of a random access preamble by thewireless device to the base station. Msg2 may be the random accessresponse (RAR) by the base station to the wireless device. Msg3 is thescheduled transmission based on an uplink grant indicated in Msg2 andMsg4 may be for contention resolution.

The base station may transmit one or more RRC messages comprisingconfiguration parameters of the random access parameters. The randomaccess parameters may indicate radio resources (e.g., time-frequencyresources) for transmission of the random access preamble (e.g., Msg1),configuration index, one or more parameters for determining the power ofthe random access preamble (e.g., a power ramping parameter, a preamblereceived target power, etc.), a parameter indicating maximum number ofpreamble transmission, RAR window for monitoring RAR, cell-specificrandom access parameters and UE specific random access parameters. TheUE-specific random access parameters may indicate one or more PRACHoccasions for random access preamble (e.g., Msg1) transmissions. Therandom access parameters may indicate association between the PRACHoccasions and one or more reference signals (e.g., SSB or CSI-RS). Therandom access parameters may further indicate association between therandom access preambles and one or more reference signals (e.g., SBB orCSI-RS). The UE may use one or more reference signals (e.g., SSB(s) orCSI-RS(s)) and may determine a random access preamble to use for Msg1transmission based on the association between the random accesspreambles and the one or more reference signals. The UE may use one ormore reference signals (e.g., SSB(s) or CSI-RS(s)) and may determine thePRACH occasion to use for Msg1 transmission based on the associationbetween the PRACH occasions and the reference signals. The UE mayperform a retransmission of the random access preamble if no response isreceived with the RAR window following the transmission of the preamble.UE may use a higher transmission power for retransmission of thepreamble. UE may determine the higher transmission power of the preamblebased on the power ramping parameter.

Msg2 is for transmission of RAR by the base station. Msg2 may comprise aplurality of RARs corresponding to a plurality of random accesspreambles transmitted by a plurality of UEs. Msg2 may be associated witha random access temporary radio identifier (RA-RNTI) and may be receivedin a common search space of the UE. The RA-RNTI may be based on thePRACH occasion (e.g., time and frequency resources of a PRACH) in whicha random access preamble is transmitted. RAR may comprise a timingadvance command for uplink timing adjustment at the UE, an uplink grantfor transmission of Msg3 and a temporary C-RNTI. In response to thesuccessful reception of Msg2, the UE may transmit the Msg3. Msg3 andMsg4 may enable contention resolution in case of CBRA. In a CBRA, aplurality of UEs may transmit the same random access preamble and mayconsider the same RAR as being corresponding to them. UE may include adevice identifier in Msg3 (e.g., a C-RNTI, temporary C-RNTI or other UEidentity). Base station may transmit the Msg4 with a PDSCH and UE mayassume that the contention resolution is successful in response to thePDSCH used for transmission of Msg4 being associated with the UEidentifier included in Msg3.

FIG. 12B shows an example of a contention-free random access (CFRA)process. Msg 1 (random access preamble) and Msg 2 (random accessresponse) in FIG. 12B for CFRA may be analogous to Msg 1 and Msg 2 inFIG. 12A for CBRA. In an example, the CFRA procedure may be initiated inresponse to a PDCCH order from a base station. The PDCCH order forinitiating the CFRA procedure by the wireless device may be based on aDCI having a first format (e.g., format 1_0). The DCI for the PDCCHorder may comprise a random access preamble index, an UL/SUL indicatorindicating an uplink carrier of a cell (e.g., normal uplink carrier orsupplementary uplink carrier) for transmission of the random accesspreamble, a SS/PBCH index indicating the SS/PBCH that may be used todetermine a RACH occasion for PRACH transmission, a PRACH mask indexindicating the RACH occasion associated with the SS/PBCH indicated bythe SS/PBCH index for PRACH transmission, etc. In an example, the CFRAprocess may be started in response to a beam failure recovery process.The wireless device may start the CFRA for the beam failure recoverywithout a command (e.g., PDCCH order) from the base station and by usingthe wireless device dedicated resources.

FIG. 12C shows an example of a two-step random access process comprisingtwo messages exchanged between a wireless device and a base station. MsgA may be transmitted by the wireless device to the base station and maycomprise one or more transmissions of a preamble and/or one or moretransmissions of a transport block. The transport block in Msg A and Msg3 in FIG. 12A may have similar and/or equivalent contents. The transportblock of Msg A may comprise data and control information (e.g., SR, HARQfeedback, etc.). In response to the transmission of Msg A, the wirelessdevice may receive Msg B from the base station. Msg B in FIG. 12C andMsg 2 (e.g., RAR) illustrated in FIGS. 12A and 12B may have similarand/or equivalent content.

The base station may periodically transmit synchronization signals(SSs), e.g., primary SS (PSS) and secondary SS (SSS) along with PBCH oneach NR cell. The PSS/SSS together with PBCH is jointly referred to as aSS/PBCH block. The SS/PBCH block enables a wireless device to find acell when entering to the mobile communications network or find newcells when moving within the network. The SS/PBCH block spans four OFDMsymbols in time domain. The PSS is transmitted in the first symbol andoccupies 127 subcarriers in frequency domain. The SSS is transmitted inthe third OFDM symbol and occupies the same 127 subcarriers as the PSS.The are eight and nine empty subcarriers on each side of the SSS. ThePBCH is transmitted on the second OFDM symbol occupying 240 subcarriers,the third OFDM symbol occupying 48 subcarriers on each side of the SSS,and on the fourth OFDM symbol occupying 240 subcarriers. Some of thePBCH resources indicated above may be used for transmission of thedemodulation reference signal (DMRS) for coherent demodulation of thePBCH. The SS/PBCH block is transmitted periodically with a periodranging from 5 ms to 160 ms. For initial cell search or for cell searchduring inactive/idle state, a wireless device may assume that that theSS/PBCH block is repeated at least every 20 ms.

In NR, transmissions using of antenna arrays, with many antennaelements, and beamforming plays an important role specially in higherfrequency bands. Beamforming enables higher capacity by increasing thesignal strength (e.g., by focusing the signal energy in a specificdirection) and by lowering the amount interference received at thewireless devices. The beamforming techniques may generally be divided toanalog beamforming and digital beamforming techniques. With digitalbeamforming, signal processing for beamforming is carried out in thedigital domain before digital-to-analog conversion and detailed controlof both amplitude and phase of different antenna elements may bepossible. With analog beamforming, the signal processing for beamformingis carried out in the analog domain and after the digital to analogconversion. The beamformed transmissions may be in one direction at atime. For example, the wireless devices that are in different directionsrelative to the base station may receive their downlink transmissions atdifferent times. For analog receiver-side beamforming, the receiver mayfocus its receiver beam in one direction at a time.

In NR, the base station may use beam sweeping for transmission ofSS/PBCH blocks. The SS/PBCH blocks may be transmitted in different beamsusing time multiplexing. The set of SS/PBCH blocks that are transmittedin one beam sweep may be referred to as a SS/PBCH block set. The periodof PBCH/SSB block transmission may be a time duration between a SS/PBCHblock transmission in a beam and the next SS/PBCH block transmission inthe same beam. The period of SS/PBCH block is, therefore, also theperiod of the SS/PBCH block set.

FIG. 13A shows example time and frequency structure of SS/PBCH blocksand their associations with beams in accordance with several of variousembodiments of the present disclosure. In this example, a SS/PBCH block(also referred to as SSB) set comprise L SSBs wherein an SSB in the SSBset is associated with (e.g., transmitted in) one of L beams of a cell.The transmission of SBBs of an SSB set may be confined within a 5 msinterval, either in a first half-frame or a second half-frame of a 10 msframe. The number of SSBs in an SSB set may depend on the frequency bandof operation. For example, the number of SSBs in a SSB set may be up tofour SSBs in frequency bands below 3 GHz enabling beam sweeping of up tofour beams, up to eight SSBs in frequency bands between 3 GHz and 6 GHzenabling beam sweeping of up to eight beams, and up to sixty four SSBsin higher frequency bands enabling beam sweeping of up to sixty fourbeams. The SSs of an SSB may depend on a physical cell identity (PCI) ofthe cell and may be independent of which beam of the cell is used fortransmission of the SSB. The PBCH of an SSB may indicate a time indexparameter and the wireless device may determine the relative position ofthe SSB within the SSB set using the time index parameter. The wirelessdevice may use the relative position of the SSB within an SSB set fordetermining the frame timing and/or determining RACH occasions for arandom access process.

A wireless device entering the mobile communications network may firstsearch for the PSS. After detecting the PSS, the wireless device maydetermine the synchronization up to the periodicity of the PSS. Bydetecting the PSS, the wireless device may determine the transmissiontiming of the SSS. The wireless device may determine the PCI of the cellafter detecting the SSS. The PBCH of a SS/PBCH block is a downlinkphysical channel that carries the MIB. The MIB may be used by thewireless device to obtain remaining system information (RMSI) that isbroadcast by the network. The RMSI may include System Information Block1 (SIB1) that contains information required for the wireless device toaccess the cell.

As discussed earlier, the wireless device may determine a time indexparameter from the SSB. The PBCH comprises a half-frame parameterindicating whether the SSB is in the first 5 ms half or the second 5 mshalf of a 10 ms frame. The wireless device may determine the frameboundary using the time index parameter and the half-frame parameter. Inaddition, the PBCH may comprise a parameter indicating the system framenumber (SFN) of the cell.

The base station may transmit CSI-RS and a UE may measure the CSI-RS toobtain channel state information (CSI). The base station may configurethe CSI-RS in a UE-specific manner. In some scenarios, same set ofCSI-RS resources may be configured for multiple UEs and one or moreresource elements of a CSI-RS resource may be shared among multiple UEs.A CSI-RS resource may be configured such that it does not collide with aCORESET configured for the wireless device and/or with a DMRS of a PDSCHscheduled for the wireless device and/or transmitted SSBs. The UE maymeasure one or more CSI-RSs configured for the UE and may generate a CSIreport based on the CSI-RS measurements and may transmit the CSI reportto the base station for scheduling, link adaptation and/or otherpurposes.

NR supports flexible CSI-RS configurations. A CSI-RS resource may beconfigured with single or multiple antenna ports and with configurabledensity. Based on the number of configured antenna ports, a CSI-RSresource may span different number of OFDM symbols (e.g., 1, 2, and 4symbols). The CSI-RS may be configured for a downlink BWP and may usethe numerology of the downlink BWP. The CSI-RS may be configured tocover the full bandwidth of the downlink BWP or a portion of thedownlink BWP. In some case, the CSI-RS may be repeated in every resourceblock of the CSI-RS bandwidth, referred to as CSI-RS with density equalto one. In some cases, the CSI-RS may be configured to be repeated inevery other resource block of the CSI-RS bandwidth. CSI-RS may benon-zero power (NZP) CSI-RS or zero-power (ZP) CSI-RS.

The base station may configure a wireless device with one or more setsof NZP CSI-RS resources. The base station may configure the wirelessdevice with a NZP CSI-RS resource set using an RRC information element(IE) NZP-CSI-RS-ResourceSet indicating a NZP CSI-RS resource setidentifier (ID) and parameters specific to the NZP CSI-RS resource set.An NZP CSI-RS resource set may comprise one or more CSI-RS resources. AnNZP CSI-RS resource set may be configured as part of the CSI measurementconfiguration.

The CSI-RS may be configured for periodic, semi-persistent or aperiodictransmission. In case of the periodic and semi-persistent CSI-RSconfigurations, the wireless device may be configured with a CSIresource periodicity and offset parameter that indicate a periodicityand corresponding offset in terms of number of slots. The wirelessdevice may determine the slots that the CSI-RSs are transmitted. Forsemi-persistent CSI-RS, the CSI-RS resources for CSI-RS transmissionsmay be activated and deactivated by using a semi-persistent (SP) CSI-CSIResource Set Activation/Deactivation MAC CE. In response to receiving aMAC CE indicating activation of semi-persistent CSI-RS resources, thewireless device may assume that the CSI-RS transmissions will continueuntil the CSI-RS resources for CSI-RS transmissions are activated.

As discussed before, CSI-RS may be configured for a wireless device asNZP CSI-RS or ZP CSI-RS. The configuration of the ZP CSI-RS may besimilar to the NZP CSI-RS with the difference that the wireless devicemay not carry out measurements for the ZP CSI-RS. By configuring ZPCSI-RS, the wireless device may assume that a scheduled PDSCH thatincludes resource elements from the ZP CSI-RS is rate matched aroundthose ZP CSI-RS resources. For example, a ZP CSI-RS resource configuredfor a wireless device may be an NZP CSI-RS resource for another wirelessdevice. For example, by configuring ZP CSI-RS resources for the wirelessdevice, the base station may indicate to the wireless device that thePDSCH scheduled for the wireless device is rate matched around the ZPCSI-RS resources.

A base station may configure a wireless device with channel stateinformation interference measurement (CSI-IM) resources. Similar to theCSI-RS configuration, configuration of locations and density of CSI-IMresources may be flexible. The CSI-IM resources may be periodic(configured with a periodicity), semi-persistent (configured with aperiodicity and activated and deactivated by MAC CE) or aperiodic(triggered by a DCI).

Tracking reference signals (TRSs) may be configured for a wirelessdevice as a set of sparse reference signals to assist the wireless intime and frequency tracking and compensating time and frequencyvariations in its local oscillator. The wireless device may further usethe TRSs for estimating channel characteristics such as delay spread ordoppler frequency. The base station may use a CSI-RS configuration forconfiguring TRS for the wireless device. The TRS may be configured as aresource set comprising multiple periodic NZP CSI-RS resources.

A base station may configure a UE and the UE may transmit soundingreference signals (SRSs) to enable uplink channel sounding/estimation atthe base station. The SRS may support up to four antenna ports and maybe designed with low cubic metric enabling efficient operation of thewireless device amplifier. The SRS may span one or more (e.g., one, twoor four) consecutive OFDM symbols in time domain and may be locatedwithin the last n (e.g., six) symbols of a slot. In the frequencydomain, the SRS may have a structure that is referred to as a combstructure and may be transmitted on every Nth subcarrier. Different SRStransmissions from different wireless devices may have different combstructures and may be multiplexed in frequency domain.

A base station may configure a wireless device with one or more SRSresource sets and an SRS resource set may comprise one or more SRSresources. The SRS resources in an SRS resources set may be configuredfor periodic, semi-persistent or aperiodic transmission. The periodicSRS and the semi-persistent SRS resources may be configured withperiodicity and offset parameters. The Semi-persistent SRS resources ofa configured semi-persistent SRS resource set may be activated ordeactivated by a semi-persistent (SP) SRS Activation/Deactivation MACCE. The set of SRS resources included in an aperiodic SRS resource setmay be activated by a DCI. A value of a field (e.g., an SRS requestfield) in the DCI may indicate activation of resources in an aperiodicSRS resource set from a plurality of SRS resource sets configured forthe wireless device.

An antenna port may be associated with one or more reference signals.The receiver may assume that the one or more reference signals,associated with the antenna port, may be used for estimating channelcorresponding to the antenna port. The reference signals may be used toderive channel state information related to the antenna port. Twoantenna ports may be referred to as quasi co-located if characteristics(e.g., large-scale properties) of the channel over which a symbol isconveyed on one antenna port may be inferred from the channel over whicha symbol is conveyed from another antenna port. For example, a UE mayassume that radio channels corresponding to two different antenna portshave the same large-scale properties if the antenna ports are specifiedas quasi co-located. In some cases, the UE may assume that two antennaports are quasi co-located based on signaling received from the basestation. Spatial quasi-colocation (QCL) between two signals may be, forexample, due to the two signals being transmitted from the same locationand in the same beam. If a receive beam is good for a signal in a groupof signals that are spatially quasi co-located, it may be assumed alsobe good for the other signals in the group of signals.

The CSI-RS in the downlink and the SRS in uplink may serve asquasi-location (QCL) reference for other physical downlink channels andphysical uplink channels, respectively. For example, a downlink physicalchannel (e.g., PDSCH or PDCCH) may be spatially quasi co-located with adownlink reference signal (e.g., CSI-RS or SSB). The wireless device maydetermine a receive beam based on measurement on the downlink referencesignal and may assume that the determined received beam is also good forreception of the physical channels (e.g., PDSCH or PDCCH) that arespatially quasi co-located with the downlink reference signal.Similarly, an uplink physical channel (e.g., PUSCH or PUCCH) may bespatially quasi co-located with an uplink reference signal (e.g., SRS).The base station may determine a receive beam based on measurement onthe uplink reference signal and may assume that the determined receivedbeam is also good for reception of the physical channels (e.g., PUSCH orPUCCH) that are spatially quasi co-located with the uplink referencesignal.

The Demodulation Reference Signals (DM-RSs) enables channel estimationfor coherent demodulation of downlink physical channels (e.g., PDSCH,PDCCH and PBH) and uplink physical channels (e.g., PUSCH and PUCCH). TheDM-RS may be located early in the transmission (e.g., front-loadedDM-RS) and may enable the receiver to obtain the channel estimate earlyand reduce the latency. The time-domain structure of the DM-RS (e.g.,symbols wherein the DM-RS are located in a slot) may be based ondifferent mapping types.

The Phase Tracking Reference Signals (PT-RSs) enables tracking andcompensation of phase variations across the transmission duration. Thephase variations may be, for example, due to oscillator phase noise. Theoscillator phase noise may become more sever in higher frequencies(e.g., mmWave frequency bands). The base station may configure the PT-RSfor uplink and/or downlink. The PT-RS configuration parameters mayindicate frequency and time density of PT-RS, maximum number of ports(e.g., uplink ports), resource element offset, configuration of uplinkPT-RS without transform precoder (e.g., CP-OFDM) or with transformprecoder (e.g., DFT-s-OFDM), etc. The subcarrier number and/or resourceblocks used for PT-RS transmission may be based on the C-RNTI of thewireless device to reduce risk of collisions between PT-RSs of wirelessdevices scheduled on overlapping frequency domain resources.

FIG. 13B shows example time and frequency structure of CSI-RSs and theirassociation with beams in accordance with several of various embodimentsof the present disclosure. A beam of the L beams shown in FIG. 13B maybe associated with a corresponding CSI-RS resource. The base station maytransmit the CSI-RSs using the configured CSI-RS resources and a UE maymeasure the CSI-RSs (e.g., received signal received power (RSRP) of theCSI-RSs) and report the CSI-RS measurements to the base station based ona reporting configuration. For example, the base station may determineone or more transmission configuration indication (TCI) states and mayindicate the one or more TCI states to the UE (e.g., using RRCsignaling, a MAC CE and/or a DCI). Based on the one or more TCI statesindicated to the UE, the UE may determine a downlink receive beam andreceive downlink transmissions using the receive beam. In case of a beamcorrespondence, the UE may determine a spatial domain filter of atransmit beam based on spatial domain filter of a corresponding receivebeam. Otherwise, the UE may perform an uplink beam selection procedureto determine the spatial domain filter of the transmit beam. The UE maytransmit one or more SRSs using the SRS resources configured for the UEand the base station may measure the SRSs and determine/select thetransmit beam for the UE based the SRS measurements. The base stationmay indicate the selected beam to the UE. The CSI-RS resources shown inFIG. 13B may be for one UE. The base station may configure differentCSI-RS resources associated with a given beam for different UEs by usingfrequency division multiplexing.

A base station and a wireless device may perform beam managementprocedures to establish beam pairs (e.g., transmit and receive beams)that jointly provide good connectivity. For example, in the downlinkdirection, the UE may perform measurements for a beam pair and estimatechannel quality for a transmit beam by the base station (or atransmission reception point (TRP) more generally) and the receive beamby the UE. The UE may transmit a report indicating beam pair qualityparameters. The report may comprise one or more parameters indicatingone or more beams (e.g., a beam index, an identifier of reference signalassociated with a beam, etc.), one or more measurement parameters (e.g.,RSRP), a precoding matrix indicator (PMI), a channel quality indicator(CQI), and/or a rank indicator (RI).

FIG. 14A, FIG. 14B and FIG. 14C show example beam management processes(referred to as P1, P2 and P3, respectively) in accordance with severalof various embodiments of the present disclosure. The P1 process shownin FIG. 14A may enable, based on UE measurements, selection of a basestation (or TRP more generally) transmit beam and/or a wireless devicereceive beam. The TRP may perform a beam sweeping procedure where theTRP may sequentially transmit reference signals (e.g., SSB and/orCSI-RS) on a set of beams and the UE may select a beam from the set ofbeams and may report the selected beam to the TRP. The P2 procedure asshown in FIG. 14B may be a beam refinement procedure. The selection ofthe TRP transmit beam and the UE receive beam may be regularlyreevaluated due to movements and/or rotations of the UE or movement ofother objects. In an example, the base station may perform the beamsweeping procedure over a smaller set of beams and the UE may select thebest beam over the smaller set. In an example, the beam shape may benarrower compared to beam selected based on the P1 procedure. Using theP3 procedure as shown in FIG. 14C, the TRP may fix its transmit beam andthe UE may refine its receive beam.

A wireless device may receive one or more messages from a base station.The one or more messages may comprise one or more RRC messages. The oneor more messages may comprise configuration parameters of a plurality ofcells for the wireless device. The plurality of cells may comprise aprimary cell and one or more secondary cells. For example, the pluralityof cells may be provided by a base station and the wireless device maycommunicate with the base station using the plurality of cells. Forexample, the plurality of cells may be provided by multiple base station(e.g., in case of dual and/or multi-connectivity). The wireless devicemay communicate with a first base station, of the multiple basestations, using one or more first cells of the plurality of cells. Thewireless device may communicate with a second base station of themultiple base stations using one or more second cells of the pluralityof cells.

The one or more messages may comprise configuration parameters used forprocesses in physical, MAC, RLC, PCDP, SDAP, and/or RRC layers of thewireless device. For example, the configuration parameters may includevalues of timers used in physical, MAC, RLC, PCDP, SDAP, and/or RRClayers. For example, the configuration parameters may include parametersfor configurating different channels (e.g., physical layer channel,logical channels, RLC channels, etc.) and/or signals (e.g., CSI-RS, SRS,etc.).

Upon starting a timer, the timer may start running until the timer isstopped or until the timer expires. A timer may be restarted if it isrunning. A timer may be started if it is not running (e.g., after thetimer is stopped or after the timer expires). A timer may be configuredwith or may be associated with a value (e.g., an initial value). Thetimer may be started or restarted with the value of the timer. The valueof the timer may indicate a time duration that the timer may be runningupon being started or restarted and until the timer expires. Theduration of a timer may not be updated until the timer is stopped orexpires (e.g., due to BWP switching). This specification may disclose aprocess that includes one or more timers. The one or more timers may beimplemented in multiple ways. For example, a timer may be used by thewireless device and/or base station to determine a time window [t1, t2],wherein the timer is started at time t1 and expires at time t2 and thewireless device and/or the base station may be interested in and/ormonitor the time window [t1, t2], for example to receive a specificsignaling. Other examples of implementation of a timer may be provided.

FIG. 15 shows example components of a wireless device and a base stationthat are in communication via an air interface in accordance withseveral of various embodiments of the present disclosure. The wirelessdevice 1502 may communicate with the base station 1542 over the airinterface 1532. The wireless device 1502 may include a plurality ofantennas. The base station 1542 may include a plurality of antennas. Theplurality of antennas at the wireless device 1502 and/or the basestation 1542 enables different types of multiple antenna techniques suchas beamforming, single-user and/or multi-user MIMO, etc.

The wireless device 1502 and the base station 1542 may have one or moreof a plurality of modules/blocks, for example RF front end (e.g., RFfront end 1530 at the wireless device 1502 and RF front end 1570 at thebase station 1542), Data Processing System (e.g., Data Processing System1524 at the wireless device 1502 and Data Processing System 1564 at thebase station 1542), Memory (e.g., Memory 1512 at the wireless device1502 and Memory 1542 at the base station 1542). Additionally, thewireless device 1502 and the base station 1542 may have othermodules/blocks such as GPS (e.g., GPS 1514 at the wireless device 1502and GPS 1554 at the base station 1542).

An RF front end module/block may include circuitry between antennas anda Data Processing System for proper conversion of signals between thesetwo modules/blocks. An RF front end may include one or more filters(e.g., Filter(s) 1526 at RF front end 1530 or Filter(s) 1566 at the RFfront end 1570), one or more amplifiers (e.g., Amplifier(s) 1528 at theRF front end 1530 and Amplifier(s) 1568 at the RF front end 1570). TheAmplifier(s) may comprise power amplifier(s) for transmission andlow-noise amplifier(s) (LNA(s)) for reception.

The Data Processing System 1524 and the Data Processing System 1564 mayprocess the data to be transmitted or the received signals byimplementing functions at different layers of the protocol stack such asPHY, MAC, RLC, etc. Example PHY layer functions that may be implementedby the Data Processing System 1524 and/or 1564 may include forward errorcorrection, interleaving, rate matching, modulation, precoding, resourcemapping, MIMO processing, etc. Similarly, one or more functions of theMAC layer, RLC layer and/or other layers may be implemented by the DataProcessing System 1524 and/or the Data Processing System 1564. One ormore processes described in the present disclosure may be implemented bythe Data Processing System 1524 and/or the Data Processing System 1564.A Data Processing System may include an RF module (RF module 1516 at theData Processing System 1524 and RF module 1556 at the Data ProcessingSystem 1564) and/or a TX/RX processor (e.g., TX/RX processor 1518 at theData Processing System 1524 and TX/RX processor 1558 at the DataProcessing System 1566) and/or a central processing unit (CPU) (e.g.,CPU 1520 at the Data Processing System 1524 and CPU 1560 at the DataProcessing System 1564) and/or a graphical processing unit (GPU) (e.g.,GPU 1522 at the Data Processing System 1524 and GPU 1562 at the DataProcessing System 1564).

The Memory 1512 may have interfaces with the Data Processing System 1524and the Memory 1552 may have interfaces with Data Processing System1564, respectively. The Memory 1512 or the Memory 1552 may includenon-transitory computer readable mediums (e.g., Storage Medium 1510 atthe Memory 1512 and Storage Medium 1550 at the Memory 1552) that maystore software code or instructions that may be executed by the DataProcessing System 1524 and Data Processing System 1564, respectively, toimplement the processes described in the present disclosure. The Memory1512 or the Memory 1552 may include random-access memory (RAM) (e.g.,RAM 1506 at the Memory 1512 or RAM 1546 at the Memory 1552) or read-onlymemory (ROM) (e.g., ROM 1508 at the Memory 1512 or ROM 1548 at theMemory 1552) to store data and/or software codes.

The Data Processing System 1524 and/or the Data Processing System 1564may be connected to other components such as a GPS module 1514 and a GPSmodule 1554, respectively, wherein the GPS module 1514 and a GPS module1554 may enable delivery of location information of the wireless device1502 to the Data Processing System 1524 and location information of thebase station 1542 to the Data Processing System 1564. One or more otherperipheral components (e.g., Peripheral Component(s) 1504 or PeripheralComponent(s) 1544) may be configured and connected to the dataProcessing System 1524 and data Processing System 1564, respectively.

In example embodiments, a wireless device may be configured withparameters and/or configuration arrangements. For example, theconfiguration of the wireless device with parameters and/orconfiguration arrangements may be based on one or more control messagesthat may be used to configure the wireless device to implement processesand/or actions. The wireless device may be configured with theparameters and/or the configuration arrangements regardless of thewireless device being in operation or not in operation. For example,software, firmware, memory, hardware and/or a combination thereof and/oralike may be configured in a wireless device regardless of the wirelessdevice being in operation or not operation. The configured parametersand/or settings may influence the actions and/or processes performed bythe wireless device when in operation.

In example embodiments, a wireless device may receive one or moremessage comprising configuration parameters. For example, the one ormore messages may comprise radio resource control (RRC) messages. Aparameter of the configuration parameters may be in at least one of theone or more messages. The one or more messages may comprise informationelement (IEs). An information element may be a structural element thatincludes single or multiple fields. The fields in an IE may beindividual contents of the IE. The terms configuration parameter, IE andfield may be used equally in this disclosure. The IEs may be implementedusing a nested structure, wherein an IE may include one or more otherIEs and an IE of the one or more other IEs may include one or moreadditional IEs. With this structure, a parent IE contains all theoffspring IEs as well. For example, a first IE containing a second IE,the second IE containing a third IE, and the third IE containing afourth IE may imply that the first IE contains the third IE and thefourth IE.

The amount of licensed spectrum available for an operator to meet thedemands may not be sufficient and obtaining licensed spectrum may becostly. Unlicensed spectrum is freely available subject to a set ofrules, for example rules on maximum transmission power. Since theunlicensed spectrum is freely available, the interference situation maybe more unpredictable compared to licensed spectrum. Achievingquality-of-service may be more challenging in unlicensed spectrum. WLANsand Bluetooth are examples of communication systems exploitingunlicensed spectrum in the lower-frequency range, e.g., 2.4 GHz or 5GHz.

Some of the frequency bands used by an NR communications system may beunlicensed (e.g., in lower and/or higher frequency bands). Differentdeployment scenarios may be used in example embodiments. Exampledeployment scenarios include: carrier aggregation between licensed bandNR (for example for PCell) and unlicensed band NR (NR-U) (for examplefor SCell), wherein NR-U SCell may have both DL and UL or may beDL-only; dual connectivity between licensed band LTE (e.g., PCell) andNR-U (e.g., PSCell); standalone NR-U, wherein PCell and SCell may beboth in unlicensed bands; an NR cell with DL in unlicensed band and ULin licensed band; and dual connectivity between licensed band NR (e.g.,PCell) and NR-U (e.g., PSCell).

In an example, the licensed spectrum may be used to provide wide-areacoverage and quality-of-service guarantees, with unlicensed spectrumused as a local-area complement to increase user data rates and overallcapacity without compromising on overall coverage, availability, andreliability. This may be referred to as License-Assisted Access (LAA).

In an example, to enable fair sharing of unlicensed spectra with otheroperators and/or systems (e.g., Wi-Fi), several mechanisms may be usedin example embodiments. Example mechanisms may include dynamic frequencyselection (DFS), where a network node may search and find a part of theunlicensed spectrum with low load. Example embodiments may employlisten-before-talk (LBT) based on example channel access procedures,where the transmitter ensures there are no ongoing transmissions on thecarrier frequency prior to transmitting.

In an example, a channel may refer to a carrier or a part of a carrieron which a channel access procedure is performed. A channel accessprocedure is a procedure based on sensing that evaluates theavailability of a channel for performing transmissions on. The basicunit for sensing may be a sensing slot with a duration T_(sl)=9 us. Thesensing slot duration T_(sl) may be considered to be idle if a basestation or a wireless device senses the channel during the sensing slotduration, and determines that the detected power for at least a portion(e.g., 4 us) within the sensing slot duration is less than an energydetection threshold (e.g., X_(Thresh)). Otherwise, the sensing slotduration T_(sl) may be considered to be busy.

A Channel Occupancy Time (COT) may refer to the total time for whicheNB/gNB/UE and eNB/gNB/UEs sharing the channel occupancy can performtransmission(s) on a channel after an eNB/gNB/UE performs thecorresponding channel access procedures. For determining a ChannelOccupancy Time, if a transmission gap is less than 25 us, the gapduration may be counted in the channel occupancy time. A channeloccupancy time may be shared for transmission between a base station andthe corresponding wireless device(s). A DL transmission burst may bedefined as a set of transmissions from a base station without gapsgreater than 16 us. Transmissions from a base station separated by a gapof more than 16 us may be considered as separate DL transmission bursts.An UL transmission burst may be defined as a set of transmissions from aUE without gaps greater than 16 us. Transmissions from a wireless deviceseparated by a gap of more than 16 us may be considered as separate ULtransmission.

In an example, a wireless device may access a channel on which uplinktransmission(s) are performed according to an uplink channel accessprocedure (e.g., one of Type 1 or Type 2 uplink channel accessprocedures). If an uplink grant scheduling a PUSCH transmissionindicates Type 1 channel access procedure, the wireless device may useType 1 channel access procedure for transmitting transmissions includingthe PUSCH transmission. A wireless device may use Type 1 channel accessprocedure for transmitting transmissions including autonomous PUSCHtransmission on configured uplink resources. If an uplink grantscheduling a PUSCH transmission indicates Type 2 channel accessprocedure, the wireless device may use Type 2 channel access procedurefor transmitting transmissions including the PUSCH transmission. Awireless device may use Type 1 channel access procedure for transmittingSRS transmissions not including a PUSCH transmission. In an example,uplink channel access priority class p=1, as shown in FIG. 16, may beused for SRS transmissions not including a PUSCH.

In an example, if a wireless device is scheduled by a base station totransmit PUSCH and SRS in contiguous transmissions without gaps inbetween, and if the wireless device cannot access the channel for PUSCHtransmission, the wireless device may attempt to make SRS transmissionaccording to uplink channel access procedures for SRS transmission.

In an example, a wireless device may use Type 1 channel access procedurefor PUCCH only transmissions or PUSCH only transmissions without UL-SCHwith UL channel access priority class p=1 in FIG. 16.

In an example, a wireless device may use Type 1 channel access procedurefor transmissions related to random access procedure with uplink channelaccess priority class p=1 in FIG. 16.

In an example, the total duration of autonomous uplink transmission(s)obtained by the channel access procedure, including the following DLtransmission if the UE sets ‘COT sharing indication’ in AUL-UCI to ‘1’in a subframe within the autonomous uplink transmission(s), may notexceed T_(ulmcot,p), where T_(ulmcot,p) is given in FIG. 16.

In an example, a wireless device may detect ‘UL duration and offset’field in a DCI. If the UL duration and offset’ field indicates an ‘ULoffset’ l and an ‘UL duration’ d for subframe n, then the scheduled UEmay use channel access Type 2 for transmissions in subframes n+l+i wherei=0, 1, . . . d−1, irrespective of the channel access Type signalled inthe UL grant for those subframes, if the end of wireless devicetransmission occurs in or before subframe n+l+d−1.

In an example, if the ‘UL duration and offset’ field indicates an ‘ULoffset’ l and an ‘UL duration’ d for subframe n and the ‘COT sharingindication for AUL’ field is set to ‘1’, a UE configured with autonomousUL may use channel access Type 2 for autonomous UL transmissionscorresponding to any priority class in subframes n+l+i where i=0, 1, . .. d−1, if the end of wireless device autonomous UL transmission occursin or before subframe n+l+d−1 and the autonomous UL transmission betweenn+l and n+l+d−1 may be contiguous.

In an example, if the ‘UL duration and offset’ field indicates an ‘ULoffset’ l and an ‘UL duration’d for subframe n and the ‘COT sharingindication for AUL’ field is set to ‘0’, then a UE configured withautonomous UL may not transmit autonomous UL in subframes n+l+i wherei=0, 1, . . . d−1.

In an example, for contiguous UL transmission(s), if a wireless deviceis scheduled to transmit a set of w UL transmissions including PUSCHusing a PDCCH DCI format, and if the wireless device cannot access thechannel for a transmission in the set prior to the last transmission,the wireless device may attempt to transmit the next transmissionaccording to the channel access type indicated in the DCI.

In an example, for contiguous uplink transmission(s), if a wirelessdevice is scheduled to transmit a set of w consecutive uplinktransmissions without gaps including PUSCH using one or more PDCCH DCIformats and the wireless device transmits one of the scheduled uplinktransmissions in the set after accessing the channel according to one ofuplink channel access procedures (e.g., Type 1 or Type 2), the wirelessdevice may continue transmission the remaining uplink transmissions inthe set, if any.

In an example, for contiguous UL transmission(s), a wireless device maynot be expected to be indicated with different channel access types forany consecutive UL transmissions without gaps in between thetransmissions.

In an example, for uplink transmission(s) with multiple startingpositions scheduled by a base station, if a wireless device is scheduledby an base station to transmit transmissions including PUSCH Mode 1using the Type 1 channel access procedure indicated in DCI, and if thewireless device cannot access the channel for a transmission accordingto the PUSCH starting position indicated in the DCI, the wireless devicemay attempt to make a transmission at symbol 7 in the same subframeaccording to Type 1 channel access procedure. In an example, there maybe no limit on the number of attempts the UE can make using Type 1channel access procedure.

In an example, for uplink transmission(s) with multiple startingpositions scheduled by a base station, if a wireless device is scheduledby a base station to transmit transmissions including PUSCH Mode 1 usingthe Type 2 channel access procedure indicated in DCI, and if thewireless device cannot access the channel for a transmission accordingto the PUSCH starting position indicated in the DCI, the wireless devicemay attempt to make a transmission at symbol 7 in the same subframe andaccording to Type 2 channel access procedure. The number of attempts thewireless device may make within the consecutively scheduled subframesincluding the transmission may be limited to w+1, where w may be thenumber of consecutively scheduled subframes using Type 2 channel accessprocedure.

In an example, for contiguous uplink transmissions(s) including atransmission pause, if the wireless is scheduled to transmit a set of wconsecutive uplink transmissions without gaps using one or more PDCCHDCI formats, and if the wireless device has stopped transmitting duringor before of one of these uplink transmissions in the set and prior tothe last uplink transmission in the set, and if the channel is sensed bythe wireless device to be continuously idle after the wireless devicehas stopped transmitting, the wireless device may transmit a lateruplink transmission in the set using Type 2 channel access procedure. Ifthe channel sensed by the wireless device is not continuously idle afterthe wireless device has stopped transmitting, the wireless device maytransmit a later uplink transmission in the set using Type 1 channelaccess procedure with the uplink channel access priority class indicatedin the DCI corresponding to the uplink transmission.

In an example, for uplink transmission(s) following configured uplinktransmission(s), if the wireless device is scheduled by a base stationto transmit on channel c_(i) by a uplink grant received on channelc_(j), i≠j, and if the wireless device is transmitting using autonomousuplink on channel c_(i), the wireless device may terminate the ongoingPUSCH transmissions using the autonomous uplink at least one subframebefore the uplink transmission according to the received uplink grant.

In an example, if the wireless device is scheduled by an uplink grantreceived from a base station on a channel to transmit a PUSCHtransmission(s) starting from subframe n on the same channel using Type1 channel access procedure and if at least for the first scheduledsubframe occupies NU resource blocks and the indicated ‘PUSCH startingposition is OFDM symbol zero, and if the wireless device startsautonomous uplink transmissions before subframe n using Type 1 channelaccess procedure on the same channel, the wireless device may transmituplink transmission(s) according to the received uplink grant fromsubframe n without a gap, if the priority class value of the performedchannel access procedure is larger than or equal to priority class valueindicated in the uplink grant, and the autonomous uplink transmission inthe subframe preceding subframe n may end at the last OFDM symbol of thesubframe regardless of the higher layer parameter endingSymbolAUL. Thesum of the lengths of the autonomous uplink transmission(s) and thescheduled uplink transmission(s) may not exceed the maximum channeloccupancy time corresponding to the priority class value used to performthe autonomous uplink channel access procedure. Otherwise, the wirelessdevice may terminate the ongoing autonomous uplink transmission at leastone subframe before the start of the uplink transmission according tothe received uplink grant on the same channel.

In an example, if a wireless device receives an uplink grant and a DCIindicating a PUSCH transmission using Type 1 channel access procedure,and if the wireless device has an ongoing Type 1 channel accessprocedure before the PUSCH transmission starting time, if the uplinkchannel access priority class value p₁ used for the ongoing Type 1channel access procedure is same or larger than the uplink channelaccess priority class value p₂ indicated in the DCI, the wireless devicemay transmit the PUSCH transmission in response to the uplink grant byaccessing the channel by using the ongoing Type 1 channel accessprocedure.

In an example, if a wireless device receives an uplink grant and a DCIindicating a PUSCH transmission using Type 1 channel access procedure,and if the wireless device has an ongoing Type 1 channel accessprocedure before the PUSCH transmission starting time, if the uplinkchannel access priority class value p₁ used for the ongoing Type 1channel access procedure is smaller than the uplink channel accesspriority class value p₂ indicated in the DCI, the wireless device mayterminate the ongoing channel access procedure.

In an example, a base station may indicate Type 2 channel accessprocedure in the DCI of an uplink grant scheduling transmission(s)including PUSCH on a channel when: the base station has transmitted onthe channel according to a channel access procedure; or base station mayindicate using the ‘UL duration and offset’ field that the wirelessdevice may perform a Type 2 channel access procedure fortransmissions(s) including PUSCH on a channel in subframe n when thebase station has transmitted on the channel according to a channelaccess procedure described; or a base station may indicate using the ‘ULduration and offset’ field and ‘COT sharing indication for AUL’ fieldthat a wireless device configured with autonomous uplink may perform aType 2 channel access procedure for autonomous uplink transmissions(s)including PUSCH on a channel in subframe n when the base station hastransmitted on the channel according to a channel access procedure andacquired the channel using the largest priority class value and the basestation transmission includes PDSCH, or a base station may scheduleuplink transmissions on a channel, that follows a transmission by thebase station on that channel with a duration of T_(short_ul)=25 us, ifthe uplink transmissions occurs within the time interval starting at t₀and ending at t₀+T_(CO), where T_(CO)=T_(m cot,p)+T_(g), where t₀ is thetime instant when the base station has started transmission, T_(m cot,p)value is determined by the base station, T_(g) is the total duration ofall gaps of duration greater than 25 us that occur between the DLtransmission of the base station and uplink transmissions scheduled bythe base station, and between any two uplink transmissions scheduled bythe base station starting from t₀.

In an example, the base station may schedule uplink transmissionsbetween to and t₀+T_(CO) without gaps between consecutive uplinktransmissions if they can be scheduled contiguously. For an uplinktransmission on a channel that follows a transmission by the basestation on that channel within a duration of T_(short_ul)=25 us, thewireless device may use Type 2A channel access procedure for the ULtransmission.

In an example, if the base station indicates Type 2 channel accessprocedure for the wireless device in the DCI, the base station mayindicate the channel access priority class used to obtain access to thechannel in the DCI.

For indicating a Type 2 channel access procedure, if the gap is at least25 us, or 16 us, or up to 16 us, the base station may indicate Type 2A,or Type 2B, or Type 2C uplink channel procedures, respectively.

In an example, if a wireless device is scheduled to transmit on a set ofchannels C, and if Type 1 channel access procedure is indicated by theuplink scheduling grants for the uplink transmissions on the set ofchannels C, and if the uplink transmissions are scheduled to starttransmissions at the same time on all channels in the set of channels C;or if the wireless device intends to perform an autonomous uplinktransmission on configured resources on the set of channels C with Type1 channel access procedure, and if UL transmissions are configured tostart transmissions on the same time all channels in the set of channelsC; and if the channel frequencies of set of channels C is a subset ofone of the sets of channel frequencies, the wireless device may transmiton channel c_(i)∈C using Type 2 channel access procedure, if Type 2channel access procedure is performed on channel c_(i) immediatelybefore the wireless device transmission on channel c_(j)∈C, i≠j, and ifthe wireless device has accessed channel c_(j) using Type 1 channelaccess procedure, where channel c is selected by the wireless deviceuniformly randomly from the set of channels C before performing Type 1channel access procedure on any channel in the set of channels C and thewireless device may not transmit on channel c_(i)∈C within the bandwidthof a carrier, if the wireless device fails to access any of thechannels, of the carrier bandwidth, on which the wireless device isscheduled or configured by UL resources.

In an example, a wireless device may transmit the transmission usingType 1 channel access procedure after first sensing the channel to beidle during the slot durations of a defer duration T_(d); and after thecounter N is zero in step 4. The counter N may be adjusted by sensingthe channel for additional slot duration(s) according to the actionsdescribed below:

1) set N=N_(init), where N_(init) is a random number uniformlydistributed between 0 and CW, and go to action 4;

2) if N>0 and the UE chooses to decrement the counter, set N=N−1;

3) sense the channel for an additional slot duration, and if theadditional slot duration is idle, go to action 4; else, go to action 5;

4) if N=0, stop; else, go to action 2.

5) sense the channel until either a busy slot is detected within anadditional defer duration T_(d) or all the slots of the additional deferduration T_(d) are detected to be idle;

6) if the channel is sensed to be idle during all the slot durations ofthe additional defer duration T_(d), go to action 4; else, go to action5;

In an example, if a wireless device has not transmitted an uplinktransmission on a channel on which uplink transmission(s) are performedafter action 4 in the process above, the wireless device may transmit atransmission on the channel, if the channel is sensed to be idle atleast in a sensing slot duration T_(sl) when the UE is ready to transmitthe transmission and if the channel has been sensed to be idle duringall the slot durations of a defer duration T_(d) immediately before thetransmission. If the channel has not been sensed to be idle in a sensingslot duration T_(sl) when the wireless device first senses the channelafter it is ready to transmit, or if the channel has not been sensed tobe idle during any of the sensing slot durations of a defer durationT_(d) immediately before the intended transmission, the wireless devicemay proceed to action 1 after sensing the channel to be idle during theslot durations of a defer duration T_(d).

The defer duration T_(d) may consist of duration T_(f)=16 us immediatelyfollowed by m_(p) consecutive slot durations where each slot duration isT_(sl)=9 us, and T_(f) includes an idle slot duration T_(sl) at start ofT_(f). CW_(min,p)≤CW_(p)≤CW_(max,p) may be the contention window.CW_(min,p) and CW_(max,p) may be chosen before step 1 of the procedureabove. m_(p), CW_(min,p), and CW_(max,p) may be based on a channelaccess priority class p as shown in FIG. 16, that is signalled to thewireless device.

In an example, if a wireless device is indicated to perform Type 2A ULchannel access procedures, the wireless device may use Type 2A ULchannel access procedure for a UL transmission. The UE may transmit thetransmission immediately after sensing the channel to be idle for atleast a sensing interval T_(short_ul)=25 us. T_(short_ul) may consist ofa duration T_(f)=16 us immediately followed by one slot durationT_(sl)=9 us and T_(f) may include an idle slot duration T_(sl) at startof T_(f). The channel may be considered to be idle for T_(short_ul) ifit is sensed to be idle during the slot durations of T_(short_ul).

In an example, if a wireless device is indicated to perform Type 2B ULchannel access procedures, the wireless device may use Type 2B ULchannel access procedure for a uplink transmission. The wireless devicemay transmit the transmission immediately after sensing the channel tobe idle.

In an example, if a wireless device is indicated to perform Type 2C ULchannel access procedures, the wireless device transmits immediatelywithout sensing the channel.

In an example embodiment, a wireless device (e.g., a MAC entity of thewireless device) may employ one or more processes to handle the uplinkLBT failures for uplink transmissions, such as uplink transmissions forone or more uplink channels (e.g., PUSCH, PUCCH and/or PRACH) and/or oneor more signals (e.g., SRS). In an example, the wireless device maydetect/determine consistent uplink LBT failures to detect/determineuplink LBT problems. A MAC entity of the wireless device may receivenotifications of uplink LBT failures from the physical layer to detectconsistent uplink LBT failures.

In an example, detection/determination of consistent uplink LBT failuresmay be based on a counter and/or timer. A value of the counter may beincremented based on detecting an uplink LBT failure. In an example, athreshold may be configured and a consistent uplink LBT failure may bedetermined based on the counter reaching the threshold. A consistentuplink LBT failure event may be triggered based on the uplink LBTfailure counter reaching the threshold value. In an example, a timer maybe started based on detecting a consistent uplink LBT failure and thevalue of the counter may be reset (e.g., reset to zero) based on anexpiry of the timer. The wireless device may receive configurationparameters indicating the threshold value for the counter (e.g., a MaxCount value) and a value of the timer. In an example, the threshold forthe counter and/or the timer value may be configured per BWP and/or percell. In an example, the threshold may be reset (e.g., reset to zero)based on the reconfiguration (e.g., in response to receiving an RRCreconfiguration message) of one or more parameters of the consistentuplink failure detection such as the threshold and/or timer value.

The wireless device may determine consistent LBT failure (e.g., for acell and/or a BWP of the cell and/or an LBT sub-band of the BWP of thecell). The wireless device may indicate the consistent LBT failure(e.g., for a cell and/or a BWP of the cell and/or an LBT sub-band of theBWP of the cell) to the base station. The cell for which the wirelessdevice may indicate consistent LBT failure may be a secondary cell or aprimary cell (e.g., PCell or PSCell). In an example, the wireless devicemay autonomously take a recovery action. In an example, the wirelessdevice may receive a command from the base station in response toindication of the consistent LBT failure to the base station. Therecovery action may include switching the BWP and/or performing a randomaccess process (e.g., in the new BWP after switching). In an example,the wireless device may stop one or more timers (e.g., BWP inactivitytimer) based on the detecting/determining the consistent LBT failure.

In an example, the determining/detecting of the consistent uplink LBTfailure on a cell/BWP may be based on a plurality of uplinktransmissions (e.g., via one or more uplink channels and/or one or moreuplink signals) on the cell/BWP. In an example, thedetermining/detecting of the consistent uplink LBT failure may beindependent of uplink transmission type. The LBT failures for differentuplink transmissions may be used to determine the consistent uplink LBTfailure regardless of the uplink transmission types (e.g., PUSCH, PUCCH,etc.). The consistent uplink LBT failure mechanism may have the samerecovery mechanism for all uplink LBT failures regardless of the uplinktransmission type.

In an example, based on detecting/determining/declaring consistentuplink LBT failures on PCell or PSCell, the wireless device may switch acurrent active BWP (of PCell or PSCell) to a second BWP (of PCell orPSCell). The wireless device may initiate a random access process in thesecond BWP based on the second BWP being configured with random accessresources. The wireless device may perform radio link failure (RLF)recovery based on the consistent uplink LBT failure being detected onthe PCell and consistent uplink LBT failure being detected on N possibleBWPs of the PCell. In an example, based on detecting/determiningconsistent uplink LBT failures on a PSCell and after detecting aconsistent uplink LBT failure on N BWPs of the PSCell, the wirelessdevice may indicate a failure to a master base station via a secondarycell group (SCG) failure information procedure. In an example, N may bethe number of configured BWPs with configured random access resources.In an example, after detecting consistent uplink LBT failure on PCell orPSCell, the wireless device may determine which BWP to switch if N islarger than one. The value of N may be configurable (e.g., via RRC) ormay be pre-determined/pre-configured.

In an example, based on detecting/determining consistent uplink LBTfailures on a cell (e.g., a SCell or PCell), the wireless device mayindicate the consistent LBT failure on the cell to the base stationbased on an LBT failure indication MAC CE. The MAC CE may reportconsistent uplink LBT failure on one or more Cells. The MAC CE formatmay support multiple entries to indicate the Cells which have alreadydeclared consistent uplink LBT failures. In an example, the LBT failureindication MAC CE may indicate/include cell index(s) where uplink LBTfailure occurs. In an example, the format of the LBT failure indicationMAC CE may be a bitmap to indicate whether corresponding serving cellhas declared consistent uplink LBT failure or not.

The LBT failure indication MAC CE may be transmitted on a differentserving cell than a SCell which has consistent UL LBT problem. In anexample, the LBT failure indication MAC CE may indicate consistentuplink LBT failures on one or more cells and the wireless device maytransmit the LBT failure indication MAC CE based on an uplink grant on acell other than the one or more cells. The MAC CE for uplink LBT failureindication may have higher priority than data but lower priority than abeam failure recovery (BFR) MAC CE.

The wireless device may trigger scheduling request if there is noavailable uplink resource for transmitting the MAC CE for a SCell uplinkLBT failure indication. The wireless device may receive configurationparameters of a SR configuration associated with uplink LBT failureindication. The configuration parameters may comprise an identifierindicating that the SR is associated with uplink LBT failure indication.In an example, when a SR configuration associated with uplink LBTfailure indication is not configured for the wireless device and noresource is available for transmitting the MAC CE for indicating SCelluplink LBT failure, the wireless device may start a random accessprocess.

In an example, when a SR for uplink LBT failure indication is triggeredand the wireless device has an overlapping SR PUCCH resource with theSCell LBT failure SR PUCCH resource, the wireless device may select theSCell LBT failure SR PUCCH resource for transmission.

In an example, the wireless device may cancel the consistent LTB failurefor a serving cell (or BWP(s)) (e.g., may not consider the cell ashaving consistent LBT failure) based on the wireless device successfullytransmitting an LBT failure MAC CE indicating the serving cell.

In an example, when consistent UL LBT failure is declared on SpCell, thewireless device may trigger MAC CE to indicate where failure happened.The MAC CE may be sent on the BWP that the wireless device switched toduring the random access process.

In an example, different LBT failures, irrespective of channel, channelaccess priority class, and LBT type, may be considered equivalent forthe consistent UL LBT failure detection procedure at a MAC entity of awireless device.

In an example, upon switching to a new BWP after detecting consistentLBT failures on a BWP of the PCell/PSCell, the wireless device mayincrement a counter (e.g., a BWP switching counter). The BWP switchingcounter may be used by the wireless device to initiate a radio linkfailure process based on the BWP switching counter reaching a value(e.g., N). The wireless device may reset the BWP switching counter whenthe random access process on a BWP of the PCell/PSCell beingsuccessfully completed.

In an example, in response to the BWP switching due to consistent uplinkLBT failure on PCell/PSCell, the wireless device may indicate theconsistent uplink LBT failure via dedicated uplink resource (e.g.PRACH). For example, the PRACH resources used for indication ofconsistent uplink LBT failure may be dedicated to consistent uplink LBTfailure indication

In an example, the uplink LBT failure information reported by the UE mayinclude one or more BWP indexes of BWPs with consistent uplink LBTfailures, one or more cell indexes of one or more cells with consistentuplink LBT failures and/or one or more measurement results (e.g.,RSRP/RSRQ/RSSI/CO) of the serving/neighbor cells

In an example, the wireless device may perform an LBT for an uplinktransmission comprising the uplink failure indication MAC CE based on ahighest priority channel access priority class (e.g., lowest numberchannel access priority).

In an example, the wireless device may reset the uplink LBT counter fora cell/BWP based on expiry of an uplink LBT timer and/or based onreceiving one or more messages indicating reconfiguration of uplink LBTconfiguration parameters for detecting consistent LBT failures and/orbased on transmitting an uplink channel or uplink signal on the cell/BWPin response to successful uplink LBT. In an example, successful uplinkLBT for the cell/BWP may indicate that the cell/BWP no longer hasconsistent LBT failures.

In an example, in response to BWP switching caused by detection ofconsistent uplink LBT failures on SpCell, a MAC entity may stop anongoing random access procedure and may initiate a new random accessprocedure.

In an example, based on switching BWP due to detecting/declaringconsistent LBT failure on a BWP of PCell or PSCell, the wireless devicemay initiate a random access process and may not perform othertransmissions (e.g., may not resume suspended configured grantstransmissions).

In an example, a wireless device may autonomously deactivate aconfigured grant for Sell(s) experiencing a consistent UL LBT failure.

In an example, based on detecting/declaring consistent uplink LBTfailure for a cell/BWP, ongoing transmissions (e.g., PUSCH transmission,SRS transmission, PUCCH transmission, RACH transmission, etc.) on activeBWP of a SCell with consistent uplink LBT failure may be suspended.

In an example, based on detecting/declaring consistent uplink LBTfailure for a cell/BWP, type 2 configured grants on the cell/BWP may becleared. In an example, based on detecting/declaring consistent uplinkLBT failure for a cell/BWP, type 1 configured grants on the cell/BWP maybe suspended. In an example, based on detecting/declaring consistentuplink LBT failure for a BWP, BWP inactivity for a downlink BWPassociated with the BWP may be stopped.

In an example, based on switching BWP due to detecting/declaringconsistent LBT failure on a BWP of PCell or PSCell, a counter fordetection of consistent uplink LBT failure of the BWP may be resetand/or a timer for consistent uplink LBT failure detection of the BWPmay be stopped.

In an example, based on an uplink transmission failure due to LBT, aphysical layer of a wireless device may send LBT failure indication to aMAC entity of the wireless device. The MAC entity of the wireless devicemay, based on receiving an LBT failure indication, start anlbt-FailureDetectionTimer and increment an LBT_COUNTER. Based on thelbt-FailureDetectionTimer expiring, the LBT_COUNTER may be reset. Basedon LBT_COUNTER reaching a configured threshold value before thelbt-FailureDetectionTimer expiring, the wireless device may trigger aconsistent uplink LBT failure event. In an example, a “failureType” inSCG failure information may indicate consistent uplink LBT failures.

In an example, the Scheduling Request (SR) may be used for requestingUL-SCH resources for new transmission. A MAC entity of a wireless devicemay be configured with zero, one, or more SR configurations. An SRconfiguration may comprise of a set of PUCCH resources for SR acrossdifferent BWPs and cells. In an example, for a logical channel, a PUCCHresource for SR may be configured per BWP.

In an example, a SR configuration may correspond to one or more logicalchannels. A logical channel may be mapped to zero or one SRconfiguration, which may be configured by RRC. The SR configuration ofthe logical channel that triggered the buffer status report (BSR) (ifsuch a configuration exists) may be considered as corresponding SRconfiguration for the triggered SR.

In an example, RRC may configure the following parameters for thescheduling request procedure: sr-ProhibitTimer (e.g., per SRconfiguration); and sr-TransMax (e.g., per SR configuration). In anexample, the following variables may be used for the scheduling requestprocedure: SR_COUNTER (e.g., per SR configuration).

In an example, if an SR is triggered and there are no other SRs pendingcorresponding to the same SR configuration, the MAC entity may set theSR_COUNTER of the corresponding SR configuration to 0.

In an example, when an SR is triggered, it may be considered as pendinguntil it is cancelled. One or more pending SR(s) triggered prior to theMAC PDU assembly may be cancelled and respective sr-ProhibitTimer may bestopped when the MAC PDU is transmitted and this PDU includes a Long orShort BSR MAC CE which contains buffer status up to (and including) thelast event that triggered a BSR prior to the MAC PDU assembly. One ormore pending SR(s) may be cancelled and respective sr-ProhibitTimer maybe stopped when the UL grant(s) can accommodate all pending dataavailable for transmission.

In an example, PUCCH resources on a BWP which is active at the time ofSR transmission occasion may be considered valid.

In an example, as long as at least one SR is pending, for each pendingSR, if the MAC entity has no valid PUCCH resource configured for thepending SR, the MAC entity may initiate a Random Access procedure on theSpCell and cancel the pending SR.

In an example, based on at least one SR is pending, for each pending SR,if the MAC entity has valid PUCCH resource configured for the pendingSR, for the SR configuration corresponding to the pending SR: when theMAC entity has an SR transmission occasion on the valid PUCCH resourcefor SR configured; and if sr-ProhibitTimer is not running at the time ofthe SR transmission occasion; and if the PUCCH resource for the SRtransmission occasion does not overlap with a measurement gap; and ifthe PUCCH resource for the SR transmission occasion does not overlapwith a UL-SCH resource: if SR_COUNTER<sr-TransMax: the wireless devicemay increment SR_COUNTER by 1; instruct the physical layer to signal theSR on one valid PUCCH resource for SR; and start the sr-ProhibitTimer.If SR_COUNTER=sr-TransMax: the wireless device may notify RRC to releasePUCCH for all Serving Cells; notify RRC to release SRS for all ServingCells; clear any configured downlink assignments and uplink grants;clear any PUSCH resources for semi-persistent CSI reporting; initiate aRandom Access procedure on the SpCell and cancel all pending SRs.

In an example, the selection of which valid PUCCH resource for SR tosignal SR on when the MAC entity has more than one overlapping validPUCCH resource for the SR transmission occasion may be based on thewireless device implementation.

In an example, if more than one individual SR triggers an instructionfrom a MAC entity to a PHY layer to signal the SR on the same validPUCCH resource, the SR_COUNTER for the relevant SR configuration may beincremented only once.

In an example, the MAC entity may stop, if any, ongoing Random Accessprocedure due to a pending SR which has no valid PUCCH resourcesconfigured, which was initiated by MAC entity prior to the MAC PDUassembly. Such a Random Access procedure may be stopped when the MAC PDUis transmitted using a UL grant other than a UL grant provided by RandomAccess Response, and this PDU includes a BSR MAC CE which containsbuffer status up to (and including) the last event that triggered a BSRprior to the MAC PDU assembly, or when the UL grant(s) can accommodateall pending data available for transmission.

In an example, a wireless device may be configured by a higher layerparameter (e.g., SchedulingRequestResourceConfig) a set ofconfigurations for SR in a PUCCH transmission for example using PUCCHformat 0 or PUCCH format 1.

The wireless device may be configured a PUCCH resource bySchedulingRequestResourceId providing a PUCCH format 0 resource or aPUCCH format 1 resource. The wireless device may also be configured aperiodicity SR_(PERIODICITY) in symbols or slots and an offsetSR_(OFFSET) in slots by periodicityAndOffset for a PUCCH transmissionconveying SR. If SR_(PERIODICITY) is larger than one slot, the UE maydetermine a SR transmission occasion in a PUCCH to be in a slot withnumber n_(s,f) ^(μ) in a frame with number n_(f) if (n_(f)·N_(slot)^(frame,μ)+n_(s,f) ^(μ)−SR_(OFFSET)) mod SR_(PERIODICITY)=0.

In an example, if SR_(PERIODICITY) is one slot, the UE may expect thatSR_(OFFSET)=0 and every slot may be a SR transmission occasion in aPUCCH.

In an example, if SR_(PERIODICITY) is smaller than one slot, the UE maydetermine a SR transmission occasion in a PUCCH to start in a symbolwith index l if (l−l₀ mod SR_(PERIODICITY)) mod SR_(PERIODICITY)=0 wherel₀ may be the value of startingSymbolIndex.

In an example, if the UE determines that, for a SR transmission occasionin a PUCCH, the number of symbols available for the PUCCH transmissionin a slot is smaller than the value provided by nrofSymbols, the UE maynot transmit the PUCCH in the slot.

In an example, the IE SchedulingRequestConfig may be used to configurethe parameters, for the dedicated scheduling request (SR) resources.

In an example, the parameter schedulingRequestToAddModList may indicatea list of Scheduling Request configurations to add or modify. Theparameter schedulingRequestToReleaseList may indicate a list ofScheduling Request configurations to release. The parameterschedulingRequestId may be used to modify a SR configuration and toindicate, in LogicalChannelConfig, the SR configuration to which alogical channel is mapped and to indicate, inSchedulingRequestresourceConfig, the SR configuration for which ascheduling request resource is used. The parameter sr-ProhibitTimer mayindicate a timer for SR transmission on PUCCH. Value is in ms. Value ms1may correspond to 1 ms, value ms2 may correspond to 2 ms, and so on.When the field is absent, the UE may apply the value 0. The parametersr-TransMax may indicate maximum number of SR transmissions. Value n4may correspond to 4, value n8 may correspond to 8, and so on.

In an example, the IE SchedulingRequestId may be used to identify aScheduling Request instance in the MAC layer.

In an example, the IE SchedulingRequestResourceConfig may determinephysical layer resources on PUCCH where the UE may send the dedicatedscheduling request (D-SR). A parameter periodicityAndOffset may indicateSR periodicity and offset in number of symbols or slots. A parameterresource may indicate an ID of the PUCCH resource in which the UE maysend the scheduling request. The actual PUCCH-Resource may be configuredin PUCCH-Config of the same UL BWP and serving cell as thisSchedulingRequestResourceConfig. The network may configure aPUCCH-Resource of PUCCH-format0 or PUCCH-format1 (other formats notsupported). The schedulingRequestID may indicate an ID of theSchedulingRequestConfig that uses this scheduling request resource.

In an example, the IE SchedulingRequestResourceId may be used toidentify scheduling request resources on PUCCH.

In an example as shown in FIG. 17, a wireless device may determineconsistent LBT failures on a cell and/or a BWP of a cell and/or an LBTsubband of a BWP of a cell. The determination of consistent LBT failureson the cell/BWP/LBT subband may be based on counting a number of uplinkLBT failures for uplink transmissions on the cell/BWP/LBT subband. Theuplink transmission may be via an uplink channel (e.g., PUSCH, PUCCH,PRACH) or an uplink signal (e.g., SRS). For example, the wireless devicemay increment a counter based on determining/detecting an uplink LBTfailure for an uplink transmission and may declare/trigger a consistentLBT failure indication based on the counter reaching a first value. Thefirst value for the counter may be configurable (e.g., by RRC). Thewireless device may receive configuration parameters comprising a firstparameter indicating the first value. For example, a MAC entity of thewireless device may determine an LBT failure based on an indication ofthe LBT failure for the uplink transmission from the physical layer ofthe wireless device. The wireless device may start a timer based onreceiving an LBT failure indication and may reset the LBT counter (e.g.,reset to zero) based on the timer expiring. The wireless device maytransmit an LBT failures indication MAC CE based on thetriggering/declaring/determining a consistent LBT failure for a firstcell/BWP/LBT subband. The LBT failures indication MAC CE may indicateconsistent LBT failure on the first cell (and/or first BWP or first LBTsubband of the first cell) and one or more other cells/BWPs/LB subbandsthat have consistent LBT failures.

In an example as shown in FIG. 18, the wireless device maydeclare/trigger consistent LBT failures on a cell/BWP/LBT subband basedon a consistent LBT failure determination described earlier. Thewireless device may determine that no uplink resource is available fortransmission of an LBT failure indication MAC CE. Based on no uplinkresource being available for transmission of the LBT failure indicationMAC CE, the wireless device may trigger a scheduling request. Thewireless device may transmit a scheduling request signal based on ascheduling request configuration. The scheduling request configurationmay be for transmission of scheduling request signals related to uplinkLBT failure recovery. In an example, as shown in FIG. 19, the wirelessdevice may transmit multiple scheduling request signals based on notreceiving an uplink grant for transmission of the consistent LBT failureMAC CE. Based on a SR counter reaching a maximum SR count, the wirelessdevice may initiate a random access process.

In an example, as shown in FIG. 20, the wireless device maydeclare/trigger consistent LBT failures on a cell/BWP/LBT subband basedon a consistent LBT failure determination described earlier. Thewireless device may determine that no uplink resource is available fortransmission of an LBT failure indication MAC CE. The wireless devicemay not be configured with a scheduling request configuration and/orscheduling request resources for consistent LBT failures recovery. Basedon no uplink resource being available for transmission of the LBTfailure indication MAC CE and no scheduling request configuration and/orscheduling request resources for consistent LBT failures recovery, thewireless device may start a random access process.

In an example, the configuration parameters of the scheduling requestconfiguration (e.g., a scheduling request identifier and/or otherparameters) may indicate that the scheduling request configuration isfor consistent LBT failure recovery. The scheduling requestconfiguration may indicate resources comprising a first resource fortransmission of the scheduling request signal.

In an example, a MAC entity of a wireless device may be configured byRRC with a beam failure recovery (BFR) procedure and with parameters fora beam failure recovery procedure. The beam failure recovery proceduremay be used for indicating to a serving base station of a new SSB orCSI-RS based on beam failure being detected on the servingSSB(s)/CSI-RS(s). Beam failure may be detected by counting beam failureinstance indications from the lower layers to the MAC entity.

In an example, if IE beamFailureRecoveryConfig is reconfigured by upperlayers during an ongoing Random Access procedure for beam failurerecovery, the MAC entity may stop the ongoing Random Access procedureand may initiate a Random Access procedure using the new configuration.

In an example, the following RRC configuration parameters may bereceived in one or more IEs such as BeamFailureRecoveryConfig and theRadioLinkMonitoringConfig for the Beam Failure Detection and Recoveryprocedure: beamFailurelnstanceMaxCount for the beam failure detection;beamFailureDetectionTimer for the beam failure detection;beamFailureRecoveryTimer for the beam failure recovery procedure;rsrp-ThresholdSSB: an RSRP threshold for the beam failure recovery;powerRampingStep: powerRampingStep for the beam failure recovery;powerRampingStepHighPriority: powerRampingStepHighPriority for the beamfailure recovery; preambleReceivedTargetPower:preambleReceivedTargetPower for the beam failure recovery;preambleTransMax: preambleTransMax for the beam failure recovery;scalingFactorBI: scalingFactorBI for the beam failure recovery;ssb-perRACH-Occasion: ssb-perRACH-Occasion for the beam failurerecovery; ra-ResponseWindow: the time window to monitor response(s) forthe beam failure recovery using contention-free Random Access Preamble;prach-ConfigurationIndex: prach-ConfigurationIndex for the beam failurerecovery; ra-ssb-OccasionMaskIndex: ra-ssb-OccasionMaskIndex for thebeam failure recovery; ra-OccasionList: ra-OccasionList for the beamfailure recovery. In an example, the UE variable BFI_COUNTER mayindicate a counter for beam failure instance indication which may beinitially set to 0.

In an example, beam failure instance indication may be received fromlower layers. The MAC entity may start or restart thebeamFailureDetectionTimer based on the receiving the beam failureinstance indication. The MAC entity may increment BFI_COUNTER by 1 basedon the receiving the beam failure instance indication. The MAC entitymay initiate a Random Access procedure on the SpCell ifBFI_COUNTER>=beamFailureInstanceMaxCount.

In an example, if the beamFailureDetectionTimer expires, the MAC entitymay set BFI_COUNTER to 0. In an example, if beamFailureDetectionTimer,beamFailureInstanceMaxCount, or the reference signals used for beamfailure detection is reconfigured by upper layers, the MAC entity mayset BFI_COUNTER to 0.

In an example, if the Random Access procedure for beam failure recoveryis successfully completed: the MAC entity may set BFI_COUNTER to 0; theMAC entity may stop the beamFailureRecoveryTimer, if configured; and theMAC entity may consider the Beam Failure Recovery procedure successfullycompleted.

In an example, an IE BeamFailureRecoveryConfig may be used to configurea wireless device with RACH resources and candidate beams for beamfailure recovery in case of beam failure detection. In an example, abeamFailureRecoveryTimer parameter may indicate a timer for beam failurerecovery timer. In an example, upon expiration of the timer the wirelessmay not use CFRA for BFR. The value of beamFailureRecoveryTimer may bein ms. For example, value ms10 may correspond to 10 ms, value ms20 maycorrespond to 20 ms, and so on. In an example, candidateBeamRSList mayindicate a list of reference signals (e.g., CSI-RS and/or SSB)identifying the candidate beams for recovery and the associated RAparameters. In an example, the network may configure these referencesignals to be within the linked DL BWP (e.g., within the DL BWP with thesame bwp-Id) of the UL BWP in which the BeamFailureRecoveryConfig may beprovided. In an example, a msg1-SubcarrierSpacing parameter may indicatesubcarrier spacing for contention free beam failure recovery. Examplevalues may include 15 kHz or 30 kHz (e.g., FR1), and 60 kHz or 120 kHz(e.g., FR2).

In an example, a rsrp-ThresholdSSB parameter may indicate L1-RSRPthreshold used for determining whether a candidate beam may be used bythe wireless device to attempt contention free random access to recoverfrom beam failure. In an example, ra-prioritization may indicateparameters which may apply for prioritized random access procedure forBFR. In an example, a ra-ssb-OccasionMaskIndex parameter may indicateexplicitly signalled PRACH Mask Index for RA Resource selection. Themask may be valid for SSB resources. In an example, a rach-ConfigBFRparameter may indicate configuration of contention free random accessoccasions for BFR. In an example, a recoverySearchSpaceld parameter mayindicate search space to use for BFR RAR. The network may configure thissearch space to be within the linked DL BWP (e.g., within the DL BWPwith the same bwp-Id) of the UL BWP in which theBeamFailureRecoveryConfig is provided. In an example, the CORESETassociated with the recovery search space may not be associated withanother search space. Network may configure the wireless device with avalue for this field when contention free random access resources forBFR are configured.

In an example, the IE RadioLinkMonitoringConfig may be used to configureradio link monitoring for detection of beam- and/or cell radio linkfailure. In an example, a beamFailureDetectionTimer parameter mayindicate a timer for beam failure detection. The value of timer may bein number of “Q_(out,LR) reporting periods of Beam Failure Detection”Reference Signal. Value pbfd1 may correspond to 1 Q_(out,LR) reportingperiod of Beam Failure Detection Reference Signal, value pbfd2 maycorrespond to 2 Q_(out,LR) reporting periods of Beam Failure DetectionReference Signal and so on. In an example, a beamFailurelnstanceMaxCountparameter may determine after how many beam failure events the wirelessdevice may trigger beam failure recovery. Value n1 may correspond to 1beam failure instance, value n2 may correspond to 2 beam failureinstances and so on. In an example, afailureDetectionResourcesToAddModList parameter may indicate a list ofreference signals for detecting beam failure and/or cell level radiolink failure (RLF). In an example, the network may configure at most twodetectionResources per BWP for the purpose beamFailure or both. If noRSs are provided for the purpose of beam failure detection, the wirelessdevice may perform beam monitoring based on the activated TCI-State forPDCCH. If no RSs are provided in this list for the purpose of RLFdetection, the wireless device may perform Cell-RLM based on theactivated TCI-State of PDCCH. The network may ensure that the wirelessdevice has a suitable set of reference signals for performing cell-RLM.

In an example, SCell beam failure detection may be per cell. In anexample, DL BWPs of a SCell may be configured with independent SCell BFRconfigurations. In an example, a SR ID may be configured for BFR withina same cell group (e.g., a PUCCH group). In an example, a SCell BFRQ MACCE may trigger a SCell BFRQ SR if there is no valid uplink grant whichcan accommodate the SCell BFRQ MAC CE. In an example, the transmissionof the SCell BFRQ MAC CE may cancel a pending BFRQ SR of the failedSCell(s). In an example, when based on the number of the BFRQ SRtransmission reaching the sr-TransMax, the wireless device may trigger aRACH procedure.

In an example, beamFailureDetectionTimer and beamFailurelnstanceMaxCountmay be configured cell specifically per DL BWP configured. In anexample, based on reconfiguration of beamFailureDetectionTimer,beamFailurelnstanceMaxCount, or any of the reference signals used forbeam failure detection by upper layers, BFI_COUNTER my be set to 0 forthe given Serving Cell. In an example, when SCell BFR SR resource is notconfigured and SCell BFR MAC CE transmission triggers SCell BFR SR,Random Access procedure on SpCell may be triggered to request ULresources to transmit the SCell BFR MAC CE.

In an example, when SCell BFR SR is triggered and the wireless devicehas an overlapping SR PUCCH resource with the SCell BFR SR PUCCHresource, the wireless device may all select the SCell BFR SR PUCCHresource for transmission. In an example, a pending SR for SCell beamfailure recovery triggered prior to the MAC PDU assembly may becancelled when the MAC PDU is transmitted and this PDU includes a SCellBFR MAC CE. In an example, SCell BFR MAC CE may carry information ofmultiple failed SCells, e.g., a multiple entry format for SCell BFR MACCE may be used.

In an example, for a SCell, the SCell BFR MAC CE may indicate thefollowing information: information about the failed SCell index,indication if new candidate beam RS is detected or not, and newcandidate beam RS index (if available). In an example, SCell BFR MAC CEmay have higher priority than data from logical channels except UL-CCCHand/or LBT failure indication MAC CE.

In an example as shown in FIG. 21, the wireless device maydeclare/trigger BFR on SCell on a cell based on a beam failure detectionprocess described earlier. The wireless device may determine that nouplink resource is available for transmission of an BFR MAC CE. Based onno uplink resource being available for transmission of the BFR MAC CE,the wireless device may trigger a scheduling request. The wirelessdevice may transmit a scheduling request signal based on a schedulingrequest configuration. The scheduling request configuration may be fortransmission of scheduling request signals related to BFR. In anexample, as shown in FIG. 22, the wireless device may transmit multiplescheduling request signals based on not receiving an uplink grant fortransmission of the BFR MAC CE. Based on a SR counter reaching a maximumSR count, the wireless device may initiate a random access process.

In an example, as shown in FIG. 23, the wireless device maydeclare/trigger BFR on SCell based on a beam failure detection processdescribed earlier. The wireless device may determine that no uplinkresource is available for transmission of a BFR MAC CE. The wirelessdevice may not be configured with a scheduling request configurationand/or scheduling request resources for BFR. Based on no uplink resourcebeing available for transmission of the BFR MAC CE and no schedulingrequest configuration and/or scheduling request resources for consistentLBT failures recovery, the wireless device may start a random accessprocess.

In an example, the configuration parameters of the scheduling requestconfiguration (e.g., a scheduling request identifier and/or otherparameters) may indicate that the scheduling request configuration isfor BFR. The scheduling request configuration may indicate resourcescomprising a first resource for transmission of the scheduling requestsignal.

In an example, a serving Cell may be configured with one or multipleBWPs. The BWP switching for a Serving Cell may be used to activate aninactive BWP and deactivate an active BWP at a time. The BWP switchingmay be controlled by the PDCCH indicating a downlink assignment or anuplink grant, by the bwp-InactivityTimer, by RRC signalling, or by theMAC entity itself upon initiation of Random Access procedure.

In an example, upon RRC (re-)configuration of firstActiveDownlinkBWP-Idand/or firstActiveUplinkBWP-Id for SpCell or activation of an SCell, theDL BWP and/or UL BWP indicated by firstActiveDownlinkBWP-Id and/orfirstActiveUplinkBWP-Id respectively may be active without receivingPDCCH indicating a downlink assignment or an uplink grant. The activeBWP for a Serving Cell may be indicated by RRC or PDCCH. For unpairedspectrum, a DL BWP may be paired with a UL BWP, and BWP switching may becommon for both UL and DL.

In an example, for an activated Serving Cell configured with a BWP, if aBWP is activated, the MAC entity may transmit on UL-SCH on the BWP;transmit on RACH on the BWP, if PRACH occasions are configured; monitorthe PDCCH on the BWP; transmit PUCCH on the BWP, if configured; reportCSI for the BWP; transmit SRS on the BWP, if configured; receive DL-SCHon the BWP; (re-)initialize suspended configured uplink grants ofconfigured grant Type 1 on the active BWP according to the storedconfiguration, if any, and to start in a symbol.

In an example, for an activated Serving Cell configured with a BWP, if aBWP is deactivated, the MAC entity may not transmit on UL-SCH on theBWP; the MAC entity may not monitor the PDCCH on the BWP; the MAC entitymay not transmit PUCCH on the BWP; the MAC entity may not report CSI forthe BWP; the MAC entity may not transmit SRS on the BWP; the MAC entitymay not receive DL-SCH on the BWP; the MAC entity may clear configureddownlink assignment and configured uplink grant of configured grant Type2 on the BWP; the MAC entity may suspend configured uplink grant ofconfigured grant Type 1 on the inactive BWP.

In an example, upon initiation of the Random Access procedure on aServing Cell, the wireless device may select a carrier for performingRandom Access procedure. The PRACH occasions may not be configured forthe active UL BWP. The MAC entity may, for the selected carrier of thisServing Cell, switch the active UL BWP to BWP indicated byinitialUplinkBWP. If the Serving Cell is an SpCell, the MAC entity may,for the selected carrier of this Serving Cell, switch the active DL BWPto BWP indicated by initialDownlinkBWP.

In an example, upon initiation of the Random Access procedure on aServing Cell, the wireless device may select a carrier for performingRandom Access procedure. The PRACH occasions may be configured for theactive UL BWP. If the Serving Cell is an SpCell, if the active DL BWPdoes not have the same bwp-Id as the active UL BWP, the MAC entity may,for the selected carrier of this Serving Cell, switch the active DL BWPto the DL BWP with the same bwp-Id as the active UL BWP.

In an example, upon initiation of the Random Access procedure on aServing Cell, the wireless device may select a carrier for performingRandom Access procedure. The MAC entity may for the selected carrier ofthis Serving Cell, stop the bwp-InactivityTimer associated with theactive DL BWP of this Serving Cell, if running. If the Serving Cell isSCell, the MAC entity may, for the selected carrier of this ServingCell, stop the bwp-InactivityTimer associated with the active DL BWP ofSpCell, if running. The MAC entity may, for the selected carrier of thisServing Cell, perform the Random Access procedure on the active DL BWPof SpCell and active UL BWP of this Serving Cell.

In an example, if the MAC entity receives a PDCCH for BWP switching of aServing Cell, if there is no ongoing Random Access procedure associatedwith this Serving Cell; or if the ongoing Random Access procedureassociated with this Serving Cell is successfully completed uponreception of this PDCCH addressed to C-RNTI, the MAC entity may performBWP switching to a BWP indicated by the PDCCH.

In an example, if the MAC entity receives a PDCCH for BWP switching fora Serving Cell while a Random Access procedure associated with thatServing Cell is ongoing in the MAC entity, it may be up to wirelessdevice implementation whether to switch BWP or ignore the PDCCH for BWPswitching, except for the PDCCH reception for BWP switching addressed tothe C-RNTI for successful Random Access procedure completion in whichcase the wireless device may perform BWP switching to a BWP indicated bythe PDCCH. Upon reception of the PDCCH for BWP switching other thansuccessful contention resolution, if the MAC entity decides to performBWP switching, the MAC entity may stop the ongoing Random Accessprocedure and initiate a Random Access procedure after performing theBWP switching; if the MAC decides to ignore the PDCCH for BWP switching,the MAC entity may continue with the ongoing Random Access procedure onthe Serving Cell.

In an example, upon reception of RRC (re-)configuration for BWPswitching for a Serving Cell while a Random Access procedure associatedwith that Serving Cell is ongoing in the MAC entity, the MAC entity maystop the ongoing Random Access procedure and initiate a Random Accessprocedure after performing the BWP switching.

In an example, the defaultDownlinkBWP-Id may be configured, and theactive DL BWP may not be the BWP indicated by the defaultDownlinkBWP-Id.In an example the defaultDownlinkBWP-Id may not configured, and theactive DL BWP may not be the initialDownlinkBWP. A PDCCH addressed toC-RNTI or CS-RNTI indicating downlink assignment or uplink grant may bereceived on the active BWP; or a PDCCH addressed to C-RNTI or CS-RNTIindicating downlink assignment or uplink grant may be received for theactive BWP; or a MAC PDU may be transmitted in a configured uplink grantor received in a configured downlink assignment. If there is no ongoingRandom Access procedure associated with this Serving Cell; or if theongoing Random Access procedure associated with this Serving Cell issuccessfully completed upon reception of this PDCCH addressed to C-RNTI:the MAC entity may start or restart the bwp-InactivityTimer associatedwith the active DL BWP.

In an example, the defaultDownlinkBWP-Id may be configured, and theactive DL BWP may not be the BWP indicated by the defaultDownlinkBWP-Id.In an example the defaultDownlinkBWP-Id may not configured, and theactive DL BWP may not be the initialDownlinkBWP. The bwp-InactivityTimerassociated with the active DL BWP may expire. If thedefaultDownlinkBWP-Id is configured, the MAC entity may perform BWPswitching to a BWP indicated by the defaultDownlinkBWP-Id. Otherwise,the MAC entity may perform BWP switching to the initialDownlinkBWP.

In an example, if a Random Access procedure is initiated on an SCell,both this SCell and the SpCell may be associated with this Random Accessprocedure.

In an example, a PDCCH for BWP switching may be received, and the MACentity may switch the active DL BWP. If the defaultDownlinkBWP-Id isconfigured, and the MAC entity switches to the DL BWP which is notindicated by the defaultDownlinkBWP-Id; or if the defaultDownlinkBWP-Idis not configured, and the MAC entity switches to the DL BWP which isnot the initialDownlinkBWP, the MAC entity may start or restart thebwp-InactivityTimer associated with the active DL BWP.

A wireless device may be configured with a beam failure recoveryprocedure and may use a beam failure detection process to detect beamfailures on the one or more serving SSBs and/or one or more servingCSI-RSs. Beam failure may be detected/determined based on a beam failuredetection process comprising counting beam failure instanceindications/notifications from the physical layer to a MAC entity. Thewireless device may start a beam failure recovery procedure based on thedetecting/determining the beam failure on a cell. The beam failurerecovery may be based on performing a random access process, for exampleon a primary cell. The wireless device may detect consistent LBTfailures on one or more cells and may perform a random access process torecover from the consistent LBT failures on the one or more cells. Whenthe one or more cells have consistent LBT failures and one or moresecond cells have beam failure, there may be a conflict between theconsistent LBT failures recovery process and the beam failure recoveryprocess. Existing solutions for beam failure and consistent LBT failurerecovery processes may lead to degraded wireless device and networkperformance. There is a need to enhance the existing beam failure andconsistent LBT failures recovery processes. Example embodiments enhancethe beam failure and consistent LBT failures recovery processes.

In an example, a wireless device may receive one or more messagescomprising configuration parameters. The one or more messages maycomprise one or more RRC messages. The one or more messages may compriseconfiguration parameters of a plurality of cells. The plurality of cellsmay comprise a first plurality of unlicensed cells. The plurality ofcells may comprise a primary cell and one or more secondary cells. Theplurality of cells may comprise a plurality of cell groups. A first cellgroup of the plurality of cell groups may be served by a first basestation (e.g., a master bae station) and a second cell group of theplurality of cell groups may be served by a second base station (e.g., asecondary base station).

In an example the plurality of cells may comprise a plurality of PUCCHgroups. A first PUCCH group (e.g., a primary PUCCH group) in theplurality of PUCCH groups may comprise a first plurality of cells, ofthe plurality of cells, comprising a primary cell, wherein the primarycell may carry first uplink control information (UCI) associated withthe first plurality of cells. A second PUCCH group in the plurality ofPUCCH groups may comprise a second plurality of cells, of the pluralityof cells, comprising a PUCCH SCell, wherein the PUCCH SCell may carrysecond UCI associated with the second plurality of cells.

The one or more messages may comprise first configuration parameters forconsistent LBT failure detection and recovery. The first configurationparameters may comprise one or more counter values for one or morecounters (e.g., one or more LBT counters) and one or more timer valuesfor one or more timers (e.g., one or more consistent uplink LBT failuredetection timers). The wireless device may employ the one or more timersand the one or more counters for consistent LBT failures detection onone or more cells. The wireless device may employ the firstconfiguration parameters for consistent LBT failure detection andrecovery on one or more cells.

The one or more messages may comprise second configuration parametersfor beam failure detection and beam failure recovery (BFR). The secondconfiguration parameters may comprise one or more counter values for oneor more counters/variables (e.g., beam failure instancecounter/variable) and one or more timer values for one or more timers(e.g., beam failure detection timer). The wireless device may employ theone or more counters/variables and the one or more timers for beamfailure detection and beam failure recovery.

In an example, the one or more messages may comprise first schedulingrequest configuration parameters for consistent LBT failure recovery.The first scheduling request configuration parameters may comprise afirst identifier indicating that the first scheduling requestconfiguration is for consistent LBT failure recovery. The firstscheduling request configuration may indicate first PUCCH resources fortransmission of scheduling requests for recovery from consistent LBTfailures on one or more cells. The first scheduling requestconfiguration may comprise first parameters (e.g., first periodicity andoffset, first PUCCH resource identifiers, etc.) indicating the firstPUCCH resources for transmission of scheduling request signals forconsistent LBT failures recovery. In an example, the one or moremessages may comprise configuration parameters of a plurality ofscheduling request configurations comprising the first schedulingrequest configuration for consistent LBT failures recovery. In anexample, the first scheduling request configuration may indicate thescheduling resources for transmission via a PUCCH of a primary celland/or via a PUCCH of a SCell configured with PUCCH. In an example, thescheduling requests for consistent LBT failures on a cell in a primaryPUUCH group may be transmitted via scheduling request resources on aprimary cell. In an example, the scheduling request signals forconsistent LBT failures on a cell in a secondary PUCCH group may betransmitted via scheduling request resources on a PUCCH SCell.

In an example, the one or more messages may comprise second schedulingrequest configuration parameters for beam failure recovery. The secondscheduling request configuration parameters may comprise a secondidentifier indicating that the second scheduling request configurationis for beam failure recovery. The second scheduling requestconfiguration may indicate second PUCCH resources for transmission ofscheduling requests for recovery from beam failure on one or more cells.The second scheduling request configuration may comprise secondparameters (e.g., second periodicity and offset, second PUCCH resourceidentifiers, etc.) indicating the second PUCCH resources fortransmission of scheduling request signals for BFR. In an example, theone or more messages may comprise configuration parameters of aplurality of scheduling request configurations comprising the secondscheduling request configuration for beam failure recovery. In anexample, the second scheduling request configuration may indicate thescheduling resources for transmission via a PUCCH of a primary celland/or via a PUCCH of a SCell configured with PUCCH. In an example, thescheduling requests for beam failure on a cell in a primary PUUCH groupmay be transmitted via scheduling request resources on a primary cell.In an example, the scheduling request signals for beam failure on a cellin a secondary PUCCH group may be transmitted via scheduling requestresources on a PUCCH SCell.

In an example, the one or more messages may comprise random accessconfiguration parameters indicating radio resources and/or RACHoccasions for transmission of random access preambles and/or randomaccess messages. The random access configuration parameters may comprisecell-specific and dedicated parameters. In an example, the cell specificand dedicated random access parameters may comprise parameters relatedto regular random access and/or random access for beam failure recovery.In an example, the cell-specific and/or dedicated random accessconfiguration parameters may comprise first parameters of random accessfor consistent LBT failures recovery.

In example embodiments as shown in FIG. 24-FIG. 26, a wireless devicemay determine consistent uplink LBT failures on one or more cells of aplurality of unlicensed cells configured for the wireless device. Thewireless device may determine the consistent LBT failures on the one ormore cells based on a consistent LBT failure detection process. Theconsistent LBT failures detection process may employ indications of LBTfailures for uplink transmissions (e.g., one or more uplink channeltransmissions, e.g., PUSCH, PUCCH and/or one or more uplink signaltransmissions, e.g., SRS) from a physical layer of the wireless deviceand may employ one or more counters (e.g., LBT counter) and one or moretimers (e.g., consistent LBT detection timer) for detection of theconsistent LBT failures.

The wireless device may start a first random access process on a primarycell based on the determining the consistent LBT failures on the one ormore cells. In an example, the one or more cells with consistent LBTfailures may comprise a primary cell. The starting the first randomaccess on the primary cell may be based on the one or more cells withconsistent LBT failures comprising the primary cell. In an example, theone or more cells with consistent LBT failures may comprise the primarycell and one or more secondary cells. In an example, based on the one ormore cells with consistent LBT failures comprising the primary cell, thewireless device may switch from a first BWP of the primary cell to asecond BWP of the primary cell and may start the first random accessprocess on the second BWP of the primary cell. The consistent LBTfailure on the primary cell may be determined on the first BWP of theprimary cell and the wireless device may switch from the first BWP ofthe primary cell to the second BWP of the primary cell and may start thefirst random access process based the consistent LBT failures on thefirst BWP of the primary cell.

In an example, the wireless device may trigger LBT failure indicationbased on the determining the consistent LBT failure on the one or morecells. The wireless device may have no uplink resources for transmissionof an uplink LBT failure indication MAC CE. The wireless device may notbe configured with a scheduling request configuration/resources forconsistent LBT failure recovery. The starting the first random access onthe primary cell may be based on the triggering the LBT failureindication, no uplink resources being available for transmission of anLBT failures indication MAC CE and no scheduling requestresource/configuration for consistent LBT failures being configured forthe wireless device.

In an example, the wireless device may trigger LBT failure indicationbased on the determining the consistent LBT failures on the one or morecells. The wireless device may have no uplink resources for transmissionof an LBT failure indication MAC CE. The wireless device may beconfigured with a scheduling request configuration for consistent LBTfailures recovery. The wireless device may trigger scheduling requestbased on no uplink resources being available for transmission of the LBTfailure indication MAC CE. The wireless device may transmit schedulingrequest signals (e.g., based on the scheduling request configuration forconsistent LBT failures recovery) and, in response to the transmittedscheduling request signals, may not receive an uplink grant useful fortransmission of the LBT failure indication MAC CE. The starting thefirst random access process may be based on transmitting schedulingrequest signals (e.g., for a maximum count of scheduling requesttransmissions) for consistent LBT failures recovery and not receiving anuplink grant for transmission of a the LBT failure indication MAC CE.The wireless device may receive a configuration parameter that indicatesthe maximum count of SR transmissions before starting a first randomaccess process.

In an example, the first random access process on the primary cell maybe a four-step random access process. The wireless device may transmit arandom access preamble based on the starting the first random accessprocess. In an example, the first random access process may be atwo-step random access process. The wireless device may transmit a Msg A(e.g., a random access preamble and a packet) based on the starting thefirst random access and the first random access process being a two-steprandom access process.

In example embodiments as shown in FIG. 24-FIG. 26, the wireless devicemay detect beam failure on a first cell. The wireless device may detectbeam failure on the first cell based on one or more serving SSBs and/orone or more serving CSI-RSs. In an example, the detecting the beamfailure on the first cell may be based on indications/notifications ofbeam failure instances from physical layer of the wireless device to aMAC entity of the wireless device. The wireless device may detect thebeam failure on the first cell based on a beam failure detection processemploying one or more counters and/or wireless device variables (e.g., aBFI_COUNTER incremented based on receiving beam failure instanceindications/notifications from physical layer) and one or more timers(e.g., beam failure detection timer).

In an example embodiment as shown in FIG. 24, based on thedetecting/determining the beam failure on the first cell, the wirelessdevice may stop the first random access process (e.g., for consistentLBT failures recovery) on the primary cell and may start a secondprocess on the primary cell for beam failure recovery. The wirelessdevice may start the second random access for beam failure recoveryafter stopping the first random access. In an example, the stopping thefirst random access process may comprise stopping transmission of arandom access preamble (or Msg A in case of two-step random access)and/or stopping monitoring control channel for random access response.In an example, the starting the second random access process maycomprise transmitting a random access preamble (e.g., for four-steprandom access process) or transmitting a Msg A (e.g., for two-steprandom access process) on the primary cell.

In an example, the wireless device may further start a third randomaccess process on the primary cell for consistent LBT failures recoverybased on the second random access for beam failure recovery beingsuccessfully completed. The wireless device may start the third randomaccess process by transmitting a random access preamble or Msg A (e.g.,in case of two-step random access) using a RACH occasion on the primarycell that occurs after the completion of second random access process.The wireless device may transmit the random access preamble or Msg Ausing a RACH occasion after receiving a random access response or Msg4/Msg B associated with the second random access process indicatingsuccessful completion of the second random access process. In anexample, the third random access process may be a two-step random accessprocess and the wireless device may transmit a Msg A based on startingthe third random access process. In an example, the third random accessprocess may be a four-step random access process and the wireless devicemay transmit a random access preamble based on starting the third randomaccess process.

In an example embodiment as shown in FIG. 25, based on thedetecting/determining the beam failure on the first cell, the wirelessdevice may continue the first random access process (e.g., forconsistent LBT failures recovery) on the primary cell. The wirelessdevice may start a second random access process on the primary cell forbeam failure recovery based on the first random access for consistentLBT failure being successfully completed. In an example, the startingthe second random access process may comprise transmitting a randomaccess preamble or transmitting a Msg A (e.g., for two-step randomaccess process) on the primary cell. The starting the second randomaccess process may comprise transmitting a random access preamble or MsgA via a RACH resource on the primary cell after receiving a randomaccess response or a Msg 4/Msg B associated with the first random accessprocess indicating successful completion of the first random accessprocess.

In an example embodiment as shown in FIG. 26, based on thedetecting/determining the beam failure on the first cell, the wirelessdevice may continue or stop the first random access process (forconsistent LBT failures recovery) on the primary cell based on a stageof the first random access process, for example depending on whether aRAR/Msg 4/Msg B has been received from the base station or depending onwhether a Msg 1/Msg A/Msg 3 has been transmitted, etc. For example, thewireless device may continue the first random access process (forconsistent LBT failures recovery) if the wireless device has received arandom access response or a Msg 4 or a Msg B and determines/detects thebeam failure on the first cell after receiving the random accessresponse or Msg 4 or Msg B. For example, the wireless device may stopthe first random access process (for consistent LBT failures recovery)if the wireless device has not received a random access response or aMsg 4 or a Msg B and determines/detects the beam failure on the firstcell before receiving the random access response or Msg 4 or Msg B.

In an example, the first cell wherein the beam failure is determined maybe a primary cell. The wireless device may start the second randomaccess process for beam failure recovery based on the first cell beingthe primary cell. In an example, a beam failure recovery process maycomprise starting a random access process based on a cell on which thebeam failure is detected being a primary cell.

In an example, the first cell wherein the beam failure is determined maybe a secondary cell. The wireless device may trigger a beam failurerecovery MAC CE. In an example, the wireless device may trigger the beamfailure recovery MAC CE based on the first cell being a secondary cell.The wireless device may have no uplink resources for transmission of thebeam failure recovery MAC CE. The starting the second random accessprocess on the primary cell for beam failure recovery may be based onthe triggering the beam failure recovery and based on no schedulingrequest resource/configuration for beam failure recovery beingconfigured for the wireless device.

In an example, the first cell wherein the beam failure is determined maybe a secondary cell. The wireless device may trigger a beam failurerecovery MAC CE. In an example, the wireless device may trigger the beamfailure recovery MAC CE based on the first cell being a secondary cell.The wireless device may have no uplink resources for transmission of thebeam failure recovery MAC CE. The wireless device may be configured witha scheduling request configuration for beam failure recovery, whereinthe scheduling request configuration may indicate scheduling requestresources for beam failure recovery. The wireless device may transmit aplurality of scheduling request signals for beam failure recovery basedon the scheduling request configuration for beam failure recovery. Theplurality of scheduling request signals may be transmitted viascheduling request resources determined based on one or more schedulingrequest configuration parameters for beam failure recovery. A number ofthe plurality of scheduling request signals may be a first number (e.g.,a maximum scheduling request count before starting a random accessprocess). The wireless device may not receive an uplink grant fortransmission of a beam failure recovery MAC CE based on the transmittingthe plurality of scheduling request signals. The starting the secondrandom access process for beam failure recovery on the primary cell maybe based the transmitting the plurality of scheduling request signalsand not receiving an uplink grant for transmission of the beam failurerecovery MAC CE.

In an example embodiment as shown in FIG. 27-FIG. 33, a wireless devicemay determine beam failure on a first cell. The wireless device maydetermine the beam failure on the first cell based on a beam failuredetection process. A beam failure instance counter/variable may reach afirst value (e.g., a beam failure instance count max value) based onreceiving indications/notifications of beam failure instances from thephysical layer. Based on the determining the beam failure on the firstcell, the wireless device may start a first random access process forbeam failure recovery. The wireless device may transmit a random accesspreamble or a Msg A (e.g., in case of a two-step random access process)based on the starting the first random access process on the primarycell.

In an example, the first cell wherein the beam failure is determined maybe a primary cell. The wireless device may start the first random accessprocess for beam failure recovery based on the first cell being theprimary cell. In an example, a beam failure recovery process maycomprise starting a random access process based on a cell on which thebeam failure is detected being a primary cell.

In an example, the first cell wherein the beam failure is determined maybe a secondary cell. The wireless device may trigger a beam failurerecovery MAC CE. In an example, the wireless device may trigger the beamfailure recovery MAC CE based on the first cell being a secondary cell.The wireless device may have no uplink resources for transmission of thebeam failure recovery MAC CE. The starting the first random accessprocess on the primary cell for beam failure recovery may be based onthe triggering the beam failure recovery and based on no schedulingrequest resource/configuration for beam failure recovery beingconfigured for the wireless device.

In an example, the first cell wherein the beam failure is determined maybe a secondary cell. The wireless device may trigger a beam failurerecovery MAC CE. In an example, the wireless device may trigger the beamfailure recovery MAC CE based on the first cell being a secondary cell.The wireless device may have no uplink resources for transmission of thebeam failure recovery MAC CE. The wireless device may be configured witha scheduling request configuration for beam failure recovery, whereinthe scheduling request configuration may indicate scheduling requestresources for beam failure recovery. The wireless device may transmit aplurality of scheduling request signals for beam failure recovery basedon the scheduling request configuration for beam failure recovery. Theplurality of scheduling request signals may be transmitted viascheduling request resources determined based on one or more schedulingrequest configuration parameters for beam failure recovery. A number ofthe plurality of scheduling request signals may be a first number (e.g.,a maximum scheduling request count before starting a random accessprocess). The wireless device may not receive an uplink grant fortransmission of a beam failure recovery MAC CE based on the transmittingthe plurality of scheduling request signals. The starting the firstrandom access process for beam failure recovery on the primary cell maybe based the transmitting the plurality of scheduling request signalsand not receiving an uplink grant for transmission of the beam failurerecovery MAC CE.

In an example, the wireless device may determine consistent LBT failureon one or more cells of a plurality of unlicensed cells configured forthe wireless device, wherein the one or more cells comprise a primarycell. The wireless device may determine the consistent LBT failures onthe one or more cells based on a consistent LBT failure detectionprocess. The consistent LBT failures detection process may employindications of LBT failures for uplink transmissions (e.g., one or moreuplink channel transmissions, e.g., PUSCH, PUCCH and/or one or moreuplink signal transmissions, e.g., SRS) from a physical layer of thewireless device and may employ one or more counters (e.g., LBT counter)and one or more timers (e.g., consistent LBT detection timer) fordetection of the consistent LBT failures.

In an example embodiment as shown in FIG. 27, FIG. 29, based on thedetermining the consistent LBT failures on the one or more cellscomprising the primary cell, the wireless device may stop the firstrandom access process. The stopping the first random access process maycomprise stopping transmission of a random access preamble (or Msg A incase of two-step random access) and/or stopping monitoring controlchannel for random access response. Based on the determining theconsistent LBT failures on the one or more cells comprising the primarycell, the wireless device may switch from a first bandwidth part of theprimary cell to a second bandwidth part of the primary cell. Thewireless device may switch from the first BWP of the primary cell to thesecond BWP of the primary cell based on the one or more cells withconsistent LBT failures comprising the primary cell.

In an example embodiment as shown on FIG. 27, the wireless device maystart a second random access process for beam failure recovery based onthe switching from the first BWP of the primary cell to the secondbandwidth part of the primary cell. The wireless device may start thesecond random access process on the second BWP of the primary cell afterswitching from the first BWP of the primary cell to the second BWP ofthe primary cell. The starting the second random access may comprisetransmitting a random access preamble or transmitting a Msg A (e.g., incase of a two-step random access) via a RACH occasion of the primarycell (e.g., on the second BWP of the primary cell).

In an example, the wireless device may start a third random accessprocess on the primary cell for consistent LBT failure recovery based onthe second random access for beam failure recovery being successfullycompleted. The wireless device may start the third random access processon the second BWP of the primary cell (e.g., after switching from thefirst BWP to the second BWP and after successful completion of thesecond random access process). The wireless device may start the thirdrandom access process on the primary cell based on the one or more cellswith consistent LBT failures comprising the primary cell. The thirdrandom access process on the primary cell may be one of a two-step orfour-step random access process. The starting the third random accessprocess may comprise transmitting a random access preamble or a Msg A(e.g., in case of a two-step random access process) via a RACH occasionthat occurs after receiving a random access response or a Msg4indicating successful completion of the second random access process.

In an example embodiment as shown in FIG. 29, the wireless device maystart a second random access process for consistent LBT failuresrecovery on the second bandwidth part of the primary cell. The startingthe second random access process may comprise transmitting a randomaccess preamble or a Msg A (e.g., in case of a two-step random access)via a RACH occasion configured for the second BWP of the primary cell.The second random access process may be successfully completed based onreceiving a random access response or a Msg 4 indicating successfulcompletion of the second random access process. The wireless device maystart a third random access process for beam failure recovery based onthe second random access for consistent LBT failures recovery beingsuccessfully completed. The wireless device may transmit a random accesspreamble or a Msg A (e.g., in case of two-step random access process)via a RACH occasion of the second bandwidth part of the second bandwidthafter the successful completion of the second random access process. Thethird random access process may be one of a two-step random accessprocess or four-step random access process.

In an example embodiment as shown in FIG. 31, based on determining theconsistent LBT failures on the one or more cells comprising the primarycell, the wireless device may continue the first random access processfor beam failure recovery. The first random access may be successfullycompleted. The successful completion of the first random access processmay be based on receiving a random access response or a Msg 4 indicatingsuccessful completion of the first random access process. The wirelessdevice may switch from the first bandwidth part of the primary cell tothe second bandwidth part of the primary cell based on the determiningthe consistent LBT failures on the one or more cells comprising theprimary cell and based on the successful completion of the first randomaccess. The wireless device may switch from the first bandwidth part ofthe primary cell to the second bandwidth part of the primary cell afterthe successful completion of the first random access and based on atiming. The wireless device may start a second random access, forconsistent LBT failures recovery, on the second BWP of the primary cell.The starting the second random access process may comprise transmittinga random access preamble or a Msg A (e.g., in case of a two-step randomaccess process).

In an example, the wireless device may determine consistent LBT failureon one or more secondary cells of a plurality of unlicensed cellsconfigured for the wireless device. The wireless device may determinethe consistent LBT failures on the one or more secondary cells based ona consistent LBT failure detection process. The consistent LBT failuresdetection process may employ indications of LBT failures for uplinktransmissions (e.g., one or more uplink channel transmissions, e.g.,PUSCH, PUCCH and/or one or more uplink signal transmissions, e.g., SRS)from a physical layer of the wireless device and may employ one or morecounters (e.g., LBT counter) and one or more timers (e.g., consistentLBT detection timer) for detection of the consistent LBT failures.

In an example embodiment as shown in FIG. 28, based on the determiningthe consistent LBT failures on the one or more secondary cells, thewireless device may continue the first random access process for beamfailure recovery. The first random access process for beam failurerecovery may be successfully completed, for example, based on receivinga random access response or a based on receiving a Msg 4/Msg Bindicating successful completion of the first random access process. Thewireless device may start a second random access process for consistentLBT failures recovery based on the first random access process beingsuccessfully completed. The starting the second random access processmay comprise transmitting a random access preamble or transmitting a MsgA (e.g., in case of a two-step random access).

In an example embodiment as shown in FIG. 30, based on the determiningthe consistent LBT failures on the one or more secondary cells, thewireless device may stop the first random access process for beamfailure recovery. The stopping the first random access process maycomprise stopping transmission of a random access preamble or Msg A(e.g., in case of two-step random access) and/or stopping monitoring arandom access response. The wireless device may start a second randomaccess process for consistent LBT failures recovery based on stoppingthe first random access process. The wireless device may start thesecond random access process after the stopping the first random accessprocess. The starting the second random access process may comprisetransmission of a random access preamble or a Msg A (e.g., for atwo-step random access process). The second random access process may besuccessfully completed based on reception of a random access response ora Msg 4/Msg B indicating successful completion of the second randomaccess process. The wireless device may start a third random accessprocess for beam failure recovery based on the second random accessprocess for consistent LBT failures being successfully completed.

In an example embodiment as show in FIG. 32, based on the determiningthe consistent LBT failures on the one or more secondary cells, thewireless device may continue the first random access process for beamfailure recovery. The first random access may be successfully completed.The successful completion of the first random access may be based onreception of a random access response or a Msg B/Msg 4 indicatingsuccessful completion of the first random access process. The wirelessdevice may start a second random access process for consistent LBTfailures recovery based on the successful completion of the first randomaccess process. The wireless device may start the second random accessprocess for consistent LBT failures recovery by transmission of a randomaccess preamble or a Msg A (e.g. in case of a two-step random accessprocess) via a RACH occasion of the primary cell after the successfulcompletion of the first random access process, e.g., after reception ofthe RAR or Msg 4/Msg B associated with the first random access processindicating the successful completion of the first random access process.

In an example, the wireless device may trigger LBT failure indicationbased on the determining the consistent LBT failures on the one or moresecondary cells. The wireless device may have no uplink resources fortransmission of an LBT failure indication MAC CE. The wireless devicemay not be configured with a scheduling request configuration/resourcesfor consistent LBT failure recovery. The starting the second randomaccess process on the primary cell may be based on the triggering theLBT failure indication, no uplink resources being available fortransmission of an LBT failures indication MAC CE and no schedulingrequest resource/configuration for consistent LBT failures beingconfigured for the wireless device.

In an example, the wireless device may trigger LBT failure indicationbased on the determining the consistent LBT failures on the one or moresecondary cells. The wireless device may have no uplink resources fortransmission of an LBT failure indication MAC CE. The wireless devicemay be configured with a scheduling request configuration for consistentLBT failures recovery. The wireless device may trigger schedulingrequest based on no uplink resources being available for transmission ofthe LBT failure indication MAC CE. The wireless device may transmitscheduling request signals (e.g., based on the scheduling requestconfiguration for consistent LBT failures recovery) and, in response tothe transmitted scheduling request signals, may not receive an uplinkgrant useful for transmission of the LBT failure indication MAC CE. Thestarting the second random access process may be based on transmittingscheduling request signals (e.g., for a maximum count of schedulingrequest transmissions) for consistent LBT failures recovery and notreceiving an uplink grant for transmission of a the LBT failureindication MAC CE. The wireless device may receive a configurationparameter that indicates the maximum count of SR transmissions beforestarting the second random access process.

In an example embodiment as shown in FIG. 33, based on the determiningthe consistent LBT failures on the one or more cells, the wirelessdevice may continue or stop the first random access process (for beamfailure recovery) on the primary cell based on a stage of the randomaccess process, for example depending on whether a RAR has been receivedfrom the base station or depending on whether a Msg 1/Msg A/Msg 3 hasbeen transmitted, etc. For example, the wireless device may continue thefirst random access process (for beam failure recovery) if the wirelessdevice has transmitted the random access preamble or Msg A anddetermines the consistent LBT failures on the one or more cells aftertransmitting the random access preamble or Msg A. The wireless devicemay stop the first random access (for beam failure recovery) if thewireless device has not transmitted the random access preamble or Msg Aand determines the consistent LBT failures on the one or more cellsbefore transmission of the random access preamble or Msg A. For example,the wireless device may continue the first random access process (forbeam failure recovery) if the wireless device has transmitted the Msg 3and determines the consistent LBT failures on the one or more cellsafter transmitting the Msg 3. The wireless device may stop the firstrandom access (for beam failure recovery) if the wireless device has nottransmitted the Msg 3 and determines the consistent LBT failures on theone or more cells before transmission of the Msg 3.

In an example, the determining the beam failure on the first cell may bebased on a beam failure instance counter/variable reaching a firstvalue. The first value may be a beam failure instance max count value.The wireless device may receive a configuration parameter indicating thebeam failure instance max count value. The wireless device may incrementthe beam failure instance counter/variable (e.g., BFI_COUNTER) based onreceiving one or more indications/notifications of a beam failureinstances from physical layer. In an example, the determining the beamfailure indication on the first cell may be based on starting a beamfailure detection timer based on receiving one or morenotifications/indications of beam failure instances from physical layer.The wireless device may reset (e.g., reset to zero) the beam failureinstance counter/variable based on the beam failure detection timerexpiring.

In an example, the first random access process may be one of a two-steprandom access process and a four-step random access process. The secondrandom access process may be one of a two-step random access process andfour-step random access process. A two-step random access process maycomprise two messages exchanged between the wireless device and the baestation (e.g., Msg A and Msg B) and a four-step random access processmay comprise four messages exchanged between the wireless device and thebase station (e.g., Msg 1/preamble, Msg 2/RAR, Msg 3 and Msg 4). In anexample, the configuration parameters may indicate whether the wirelessdevice may start a two-step or a four-step random access process forconsistent LBT failure recovery. In an example, the configurationparameters may indicate whether the wireless device may start a two-stepor a four-step random access process for beam failure recovery. In anexample, the wireless device may receive configuration parametersindicating one or more first random access parameters (e.g., one orfirst threshold values, one or more first prioritization parameters, oneor more first power parameters (e.g., power ramping parameter) forcalculating a preamble power, etc.) for a random access process forconsistent LBT failure recovery. In an example, the wireless device mayreceive configuration parameters indicating one or more second randomaccess parameters (e.g., one or second threshold values, one or moresecond prioritization parameters, one or more first power parameters(e.g., power ramping parameter) for calculating a preamble power, etc.)for a random access process for beam failure recovery.

In an example embodiment, a wireless device may start a first randomaccess process on a primary cell based on determining consistent LBTfailures on one or more cells. The wireless device may transmit a randomaccess preamble based on determining the consistent LBT failure on oneor more cells and starting the first random access process. In anexample, the wireless device may transmit a Msg A based on determiningconsistent LBT failure on one or more cells and starting the firstrandom access process (e.g., with two-step random access). The wirelessdevice may determine a beam failure on a first cell. Based on thedetermining the beam failure: the wireless device may stop the firstrandom access process; and the wireless device may start a second randomaccess process on the primary cell for beam failure recovery. Thewireless device may start the second random access process afterstopping the first random access process.

In an example embodiment, a wireless device may start a first randomaccess process on a primary cell based on determining consistent LBTfailures on one or more cells. The wireless device may transmit a randomaccess preamble based on determining the consistent LBT failure on oneor more cells and starting the first random access process. In anexample, the wireless device may transmit a Msg A based on determiningthe consistent LBT failure on one or more cells and starting the firstrandom access process (e.g., with two-step random access). The wirelessdevice may determine a beam failure on a first cell. Based on thedetermining the beam failure on the first cell: the wireless device maycontinue the first random access process; and the wireless device maystart a second random access process on the primary cell for beamfailures recovery based on the first random access being successfullycompleted.

In an example, the one or more cells may with consistent LBT failurescomprise the primary cell. In an example, the starting the first randomaccess process on the primary cell may be based on the one or more cellswith consistent LBT failures compromising the primary cell. In anexample, based on the one or more cells with consistent LBT failurescomprising the primary cell, the wireless device may switch from a firstbandwidth part of the primary cell to a second bandwidth part of theprimary cell and may start the first random access process on the secondbandwidth part of the primary cell.

In an example, the wireless device may trigger an LBT failure indicationdue to determining the consistent LBT failures on the one or more cells.The wireless device may have no uplink resources being available fortransmission of a consistent LBT failure indication MAC CE. In anexample, no scheduling request resource for consistent LBT failurerecovery may be configured for the wireless device. The wireless devicemay start the first random access process based on no scheduling requestresource for consistent LBT failure recovery being configured for thewireless device.

In an example, the wireless device may trigger an LBT failure indicationdue to determining the consistent LBT failures on the one or more cells.The wireless device may have no uplink resources being available fortransmission of a consistent LBT failure MAC CE. The wireless device maytrigger scheduling request based on no uplink resources being availablefor transmission of a consistent LBT failure MAC CE. In an example, thewireless device may start the first random access process based on:transmitting scheduling request signals for consistent LBT failuresrecovery; and not receiving an uplink grant for transmission of aconsistent LBT indication MAC CE.

In an example, the wireless device may start a third random accessprocess on the primary cell for consistent LBT failure recovery based onthe second random access process for beam failure recovery beingsuccessfully completed. The third random access process may be one of atwo-step random access process or a four-step random access process.

In an example, the first cell with beam failure may be a primary cell.The wireless may start the second random access on the primary cellbased on the first cell with beam failure being the primary cell.

In an example, the first cell with beam failure may be a secondary cell.The wireless device may trigger a beam failure recovery MAC CE based onthe first cell with beam failure being a secondary cell. The wirelessdevice may have no uplink resources available for transmission of thebeam failure recovery MAC CE. The starting the second random access onthe primary cell may be based on no scheduling request resource for beamfailure recovery being configured for the wireless device.

In an example, the first cell with beam failure may be a secondary cell.The wireless device may trigger a beam failure recovery MAC CE based onthe first cell with beam failure being a secondary cell. The wirelessdevice may have no uplink resources available for transmission of thebeam failure recovery MAC CE. The wireless device may trigger schedulingrequest and may transmit a plurality of scheduling request signals forbeam failure recovery. The wireless device may not receive an uplinkgrant for transmission of a beam failure recovery MAC CE. The startingthe second random access on the primary cell may be based on notreceiving an uplink grant for transmission of a beam failure recoveryMAC CE.

In an example embodiment, a wireless device may start a first randomaccess process on a primary cell based on determining a beam failure ona first cell. The wireless device may transmit a random access preamblebased on determining the beam failure on the first cell and starting thefirst random access process. In an example, the wireless device maytransmit a Msg A based on determining the beam failure on the first celland starting the random access process (e.g., with two-step randomaccess). The wireless device may determine consistent LBT failures onone or more cells comprising the primary cell. Based on the determining:the wireless device may stop the first random access process; thewireless device may switch from the first bandwidth part of the primarycell to a second bandwidth part of the primary cell; and the wirelessdevice may start a second random access process for beam failurerecovery.

In an example, the wireless device may start a third random access onthe primary cell for consistent LBT failure recovery based on the secondrandom access process being successfully completed. In an example, thestarting the third random access process on the primary cell may bebased on the one or more cells with consistent LBT failures comprisingthe primary cell. In an example, the wireless device may start the thirdrandom access on the second bandwidth part of the primary cell. Thethird random access process may be a two-step random access or afour-step random access.

In an example, the switching from the first bandwidth part of theprimary cell to the second bandwidth part of the primary cell may bebased on the one or more cells with consistent LBT failures comprisingthe primary cell.

In an example, the first cell with beam failure may be a primary cell.The wireless may start the first random access on the primary cell basedon the first cell with beam failure being the primary cell.

In an example, the first cell with beam failure may be a secondary cell.The wireless device may trigger a beam failure recovery MAC CE based onthe first cell with beam failure being a secondary cell. The wirelessdevice may have no uplink resources available for transmission of thebeam failure recovery MAC CE. The starting the first random access onthe primary cell may be based on no scheduling request resource for beamfailure recovery being configured for the wireless device.

In an example, the first cell with beam failure may be a secondary cell.The wireless device may trigger a beam failure recovery MAC CE based onthe first cell with beam failure being a secondary cell. The wirelessdevice may have no uplink resources available for transmission of thebeam failure recovery MAC CE. The wireless device may trigger schedulingrequest and may transmit a plurality of scheduling request signals forbeam failure recovery. The wireless device may not receive an uplinkgrant for transmission of a beam failure recovery MAC CE. The startingthe first random access on the primary cell may be based on notreceiving an uplink grant for transmission of a beam failure recoveryMAC CE.

In an example embodiment, a wireless device may start a first randomaccess process on a primary cell based on determining a beam failure ona first cell. The wireless device may transmit a random access preamblebased on determining the beam failure on the first cell and starting thefirst random access process. In an example, the wireless device maytransmit a Msg A based on determining the beam failure on the first celland starting the random access process (e.g., with two-step randomaccess). The wireless device may determine consistent LBT failures onone or more secondary cells. Based on the determining: the wirelessdevice may continue the first random access process; and the wirelessdevice may start a second random access process for consistent LBTfailures recovery based on the first random access process beingsuccessfully completed.

In an example, the wireless device may trigger consistent LBT failureindication. The wireless device may have no uplink resources availablefor transmission of a consistent LBT failure indication MAC CE. In anexample, the starting the second random access process may be based onno scheduling request resource for consistent LBT failures recoverybeing configured for the wireless device.

In an example, the wireless device may trigger consistent LBT failureindication. The wireless device may have no uplink resources availablefor transmission of a consistent LBT failure indication MAC CE. Thewireless device may trigger scheduling request based on no uplinkresources being available for transmission of a consistent LBT failureindication MAC CE. The wireless device may start the second randomaccess process based on transmitting scheduling request signals forconsistent LBT failures recovery; and not receiving an uplink grant fortransmission of a consistent LBT failure indication MAC CE.

In an example, the first cell with beam failure may be a primary cell.The wireless may start the first random access on the primary cell basedon the first cell with beam failure being the primary cell.

In an example, the first cell with beam failure may be a secondary cell.The wireless device may trigger a beam failure recovery MAC CE based onthe first cell with beam failure being a secondary cell. The wirelessdevice may have no uplink resources available for transmission of thebeam failure recovery MAC CE. The starting the first random access onthe primary cell may be based on no scheduling request resource for beamfailure recovery being configured for the wireless device.

In an example, the first cell with beam failure may be a secondary cell.The wireless device may trigger a beam failure recovery MAC CE based onthe first cell with beam failure being a secondary cell. The wirelessdevice may have no uplink resources available for transmission of thebeam failure recovery MAC CE. The wireless device may trigger schedulingrequest and may transmit a plurality of scheduling request signals forbeam failure recovery. The wireless device may not receive an uplinkgrant for transmission of a beam failure recovery MAC CE. The startingthe first random access on the primary cell may be based on notreceiving an uplink grant for transmission of a beam failure recoveryMAC CE.

In an example embodiment, a wireless device may start a first randomaccess process on a primary cell for beam failure recovery based ondetermining a beam failure on a first cell. The wireless device maytransmit a random access preamble based on determining the beam failureon the first cell and starting the first random access process. In anexample, the wireless device may transmit a Msg A based on determiningthe beam failure on the first cell and starting the random accessprocess (e.g., with two-step random access). The wireless device maydetermine consistent LBT failures on one or more cells comprising theprimary cell. Based on the determining: the wireless device may stop thefirst random access process; the wireless device may switch from a firstbandwidth part of the primary cell to a second bandwidth part of theprimary cell; the wireless device may start a second random accessprocess, for consistent LBT failures recovery, on the second bandwidthpart; and the wireless device may start a third random access processfor beam failure recovery based on the second random access processbeing successfully completed.

In an example, the switching from the first bandwidth part of theprimary cell to the second bandwidth part of the primary cell may bebased on the one or more cells with consistent LBT failures comprisingthe primary cell. In an example, the starting the second random accessprocess on the primary cell may be based on the one or more cells withconsistent LBT failures comprising the primary cell.

In an example, the starting the third random access process may be onthe second bandwidth part of the primary cell. In an example, the thirdrandom access may be one of a two-step random access and a four-steprandom access.

In an example, the first cell with beam failure may be a primary cell.The wireless may start the first random access on the primary cell basedon the first cell with beam failure being the primary cell.

In an example, the first cell with beam failure may be a secondary cell.The wireless device may trigger a beam failure recovery MAC CE based onthe first cell with beam failure being a secondary cell. The wirelessdevice may have no uplink resources available for transmission of thebeam failure recovery MAC CE. The starting the first random access onthe primary cell may be based on no scheduling request resource for beamfailure recovery being configured for the wireless device.

In an example, the first cell with beam failure may be a secondary cell.The wireless device may trigger a beam failure recovery MAC CE based onthe first cell with beam failure being a secondary cell. The wirelessdevice may have no uplink resources available for transmission of thebeam failure recovery MAC CE. The wireless device may trigger schedulingrequest and may transmit a plurality of scheduling request signals forbeam failure recovery. The wireless device may not receive an uplinkgrant for transmission of a beam failure recovery MAC CE. The startingthe first random access on the primary cell may be based on notreceiving an uplink grant for transmission of a beam failure recoveryMAC CE.

In an example embodiment, a wireless device may start a first randomaccess process on a primary cell for beam failure recovery based ondetermining a beam failure on a first cell. The wireless device maytransmit a random access preamble based on determining the beam failureon the first cell and starting the first random access process. In anexample, the wireless device may transmit a Msg A based on determiningthe beam failure on the first cell and starting the random accessprocess (e.g., with two-step random access). The wireless device maydetermine consistent LBT failures on one or more secondary cells. Basedon the determining: the wireless device may stop the first random accessprocess; the wireless device may start a second random access processfor consistent LBT failures recovery; and the wireless device may starta third random access process, for consistent LBT failures recovery,based on the second random access process being successfully completed.

In an example, the wireless device may trigger an LBT failure indicationbased on the consistent LBT failures on the one or more secondary cells.The wireless device may be configured with no uplink resources fortransmission of an LBT failures indication MAC CE. In an example, thestarting the second random access process may be based on no schedulingrequest resource for consistent LBT failures recovery being configuredfor the wireless device.

In an example, the wireless device may trigger an LBT failure indicationbased on the consistent LBT failures on the one or more secondary cells.The wireless device may be configured with no uplink resources fortransmission of an LBT failures indication MAC CE. The wireless devicemay trigger scheduling request. In an example, the starting the secondrandom access process may be based on transmitting scheduling requestsignals for consistent LBT failures recovery; and not receiving anuplink grant for transmission of a consistent LBT failure indication MACCE.

In an example, the first cell with beam failure may be a primary cell.The wireless may start the first random access on the primary cell basedon the first cell with beam failure being the primary cell.

In an example, the first cell with beam failure may be a secondary cell.The wireless device may trigger a beam failure recovery MAC CE based onthe first cell with beam failure being a secondary cell. The wirelessdevice may have no uplink resources available for transmission of thebeam failure recovery MAC CE. The starting the first random access onthe primary cell may be based on no scheduling request resource for beamfailure recovery being configured for the wireless device.

In an example, the first cell with beam failure may be a secondary cell.The wireless device may trigger a beam failure recovery MAC CE based onthe first cell with beam failure being a secondary cell. The wirelessdevice may have no uplink resources available for transmission of thebeam failure recovery MAC CE. The wireless device may trigger schedulingrequest and may transmit a plurality of scheduling request signals forbeam failure recovery. The wireless device may not receive an uplinkgrant for transmission of a beam failure recovery MAC CE. The startingthe first random access on the primary cell may be based on notreceiving an uplink grant for transmission of a beam failure recoveryMAC CE.

In an example embodiment, a wireless device may start a first randomaccess process on a primary cell for beam failure recovery based ondetermining a beam failure on a first cell. The wireless device maytransmit a random access preamble based on determining the beam failureon the first cell and starting the first random access process. In anexample, the wireless device may transmit a Msg A based on determiningthe beam failure on the first cell and starting the random accessprocess (e.g., with two-step random access). The wireless device maydetermine consistent LBT failures on one or more cells comprising aprimary cell. Based on the determining the consistent LBT failures: thewireless device may continue the first random access process; thewireless device may switch from a first bandwidth part of the primarycell to a second bandwidth part of the primary cell based on the firstrandom access process being successfully completed; and the wirelessdevice may start a second random access process for consistent LBTfailures recovery on the second bandwidth part.

In an example embodiment, a wireless device may start a first randomaccess process on a primary cell for beam failure recovery based ondetermining a beam failure on a first cell. The wireless device maytransmit a random access preamble based on determining the beam failureon the first cell and starting the first random access process. In anexample, the wireless device may transmit a Msg A based on determiningthe beam failure on the first cell and starting the random accessprocess (e.g., with two-step random access). The wireless device maydetermine consistent LBT failures on one or more secondary cells. Basedon the determining the consistent LBT failures: the wireless device maycontinue the first random access process; and the wireless device maystart a second random access process for consistent LBT failuresrecovery based on the first random access process being successfullycompleted.

In an example, the determining the beam failure on the first cell may bebased on a beam failure detection counter reaching a first value. In anexample, the determining the beam failure on the first cell may compriseincrementing a beam failure detection counter based on one or morenotifications of beam failure instances from physical layer. In anexample, the determining the beam failure on the first cell may comprisestarting a beam failure detection timer based on one or morenotifications of beam failure instances from physical layer. In anexample, the determining the beam failure on the first cell may comprisecomprises resetting a beam failure detection counter (e.g., resetting tozero) based on a beam failure detection timer expiring.

In an example, the first random access process may be one of a two-steprandom access or a four-step random access process; and the secondrandom access process may be one of a two-step random access or afour-step random access process.

In an example, the wireless device may receive configuration parameterscomprising: random access configuration parameters; beam failuredetection and recovery configuration parameters; and consistent LBTfailure detection and recovery configuration parameters. The randomaccess configuration parameters may comprise one or more parametersindicating random access occasions on one or more bandwidth parts of theprimary cell. The beam failure detection and recovery configurationparameters may comprise one or more second parameters (e.g., one or morecounter and/or timer values) for detection of a beam failure based on abeam failure detection process and for recovery based on a beam failurerecovery process. The consistent LBT failure detection and recoveryconfiguration parameters may comprise one or more third parameters(e.g., one or more counter and/or timer values) for detection ofconsistent LBT failures on a cell based on a consistent LBT failuresdetection process and for recovery based on a consistent LBT failuresrecovery process.

Existing procedures for recovery from consistent listen before talk on aprimary cell or recovery from beam failure on a primary cell may bebased on initiation of a random access process. The existing proceduresmay not take into account the ongoing random access process processeswhen the recovery procedure is initiated and may lead to wireless deviceand network performance degradation, for example due to increasedlatency or inefficiency or failure of the recovery procedures. There isa need to enhance the existing consistent LBT failure recovery and/orbeam failure recovery procedures. Example embodiments enhance theexisting consistent LBT failure and/or beam failure recovery procedures.

In an example embodiment, a wireless device may receive one or moremessages (e.g., one or more RRC messages) comprising configurationparameters. The configuration parameters may comprise serving cellconfiguration parameters of one or more cells. The one or more cells maycomprise a primary cell. In an example, the one or more cells maycomprise a primary cell and one or more secondary cells. In an example,the one or more cells may comprise an unlicensed cell or a cell thatoperates in unlicensed spectrum or shared spectrum. In an example, theprimary cell may be an unlicensed cell or a cell that operates inunlicensed spectrum or shared spectrum. The uplink and/or downlinktransmissions on a cell that operates in the unlicensed or sharedspectrum may be based on a listen-before-talk (LBT) procedure, for theuplink and/or the downlink transmission, indicating that the channel isavailable for transmission. In an example, the one or more cells may beprovided by one or more base stations, e.g., using a single-connectivityarchitecture or multi-connectivity architecture. In an example, a cell(e.g., the primary cell) in the one or more cells may operate usingbeamforming, for example, the cell may be associated with multiplebeams. The configuration parameters may comprise first configurationparameters for beam failure recovery and second configuration parametersfor LBT failure recovery. The wireless device maydetect/determine/trigger and recover from beam failure based on theconfiguration parameters for beam failure recovery. The wireless devicemay detect/determine/trigger and recover from consistent LBT failurebased on the configuration parameters for LBT failure recovery.

The configuration parameters for beam failure recovery may be based on aBeamFailureRecoveryConfig information element (IE) and/or aRadioLinkMonitoringConfig IE. The BeamFailureRecoveryConfig IE may beused to configure the UE with RACH resources and candidate beams forbeam failure recovery in case of beam failure detection. TheBeamFailureRecoveryConfig IE may comprise a plurality offields/parameters. A beamFailureRecoveryTimer field may indicate a timerfor beam failure recovery timer. Upon expiration of the timer the UE maynot use CFRA for beam failure recovery (BFR). A candidateBeamRSListfield may indicate the list of reference signals (e.g., CSI-RS and/orSSB) identifying the candidate beams for recovery and the associatedrandom access parameters. A msg1-SubcarrierSpacing field may indicate asubcarrier spacing for contention free beam failure recovery. Arsrp-ThresholdSSB field may indicate a L1-RSRP threshold used fordetermining whether a candidate beam may be used by the UE to attemptcontention free random access to recover from beam failure. Ara-prioritization field may indicate parameters which may apply forprioritized random access procedure for BFR. A ra-PrioritizationTwoStepfield may indicate parameters which may apply for prioritized 2-steprandom access procedure for BFR. A ra-ssb-OccasionMaskIndex field mayindicate an explicitly signaled PRACH Mask Index for RA Resourceselection. A rach-ConfigBFR field may indicate configuration ofcontention free random access occasions for BFR. A recoverySearchSpaceldfield may indicate search space to use for BFR RAR, e.g., for receptionof random access response (RAR) in random access process initiated forbeam failure recovery. The network may configure this search space to bewithin the linked DL BWP (e.g., within the DL BWP with the same bwp-Id)of the UL BWP in which the BeamFailureRecoveryConfig is provided. In anexample, the CORESET associated with the recovery search space may notbe associated with another search space. The network may configure theUE with a value for this field when contention free random accessresources for BFR are configured. A rootSequenceIndex-BFR field mayindicate PRACH root sequence index for beam failure recovery. Assb-perRACH-Occasion field may indicate a number of SSBs per RACHoccasion for CF-BFR.

A RadioLinkMonitoringConfig IE may be used to configure radio linkmonitoring for detection of beam- and/or cell radio link failure. TheRadioLinkMonitoringConfig IE may comprise a plurality of field. AbeamFailureDetectionTimer field may indicate a timer for beam failuredetection. A beamFailurelnstanceMaxCount field may be used to determineafter how many beam failure events the UE may trigger beam failurerecovery. A failureDetectionResourcesToAddModList field may indicate alist of reference signals for detecting beam failure and/or cell levelradio link failure (RLF).

The configuration parameters for LBT failure recovery may be based on anLBT-FailureRecoveryConfig IE. The LBT-FailureRecoveryConfig IE may beused to configure the parameters used for detection of consistent uplinkLBT failures for operation with shared spectrum channel access. TheLBT-FailureRecoveryConfig IE may comprise a plurality ofparameters/fields. An lbt-FailureDetectionTimer field may indicate atimer for consistent uplink LBT failure detection. Anlbt-FailurelnstanceMaxCount field may determine after how manyconsistent uplink LBT failure events the UE may trigger uplink LBTfailure recovery.

In an example embodiment as shown in FIG. 34, the wireless device maydetect a beam failure on a primary cell of the wireless device. Thefirst configuration for beam failure recovery may comprise a firstparameter (e.g., beamFailurelnstanceMaxCount) indicating a first numberof beam failure instances that triggers beam failure recovery. Thedetection of the beam failure may be based on a beam failure instanceindication counter reaching the first number. In an example, thewireless device may increment the beam failure instance indicationcounter by one based on a beam failure indication, for example receptionof the beam failure indication by a MAC layer of the wireless devicefrom a physical layer of the wireless device. The wireless device maystart or restart a beam failure detection timer in response to the beamfailure indication, e.g., reception of the beam failure indication bythe MAC layer from the physical layer. The wireless device may set thebeam failure instance indication counter to zero (e.g., reset the beamfailure instance indication counter) based on the beam failure detectiontimer expiring. In response to the detection of the beam failure on theprimary cell, the wireless device may initiate a first random accessprocess on a first BWP of the primary cell. The first BWP of the primarycell may be the current active BWP (e.g., the active BWP of the primarycell when the wireless device detects the beam failure on the primarycell) of the primary cell. The wireless device may initiate the firstrandom access process on the first BWP of the primary cell for beamfailure recovery.

The wireless device may trigger consistent LBT failure for the primarycell. The wireless device may trigger the consistent LBT failure for theprimary cell while the first random access process for beam failurerecovery is ongoing on the primary cell. The triggering of theconsistent LBT failure may be for the first BWP of the primary celland/or based on failure of LBT procedures for uplink transmissions onthe first BWP of the primary cell. The second configuration for LBTfailure recovery may comprise a first parameter (e.g.,FailureInstanceMaxCount) indicating a first number of LBT failureinstances that triggers LBT failure recovery. The triggering of theconsistent LBT failure may be based on an LBT failure indication counterreaching the first number. In an example, the wireless device mayincrement the LBT failure indication counter by one based on an LBTfailure indication, for example reception of the LBT failure indicationby a MAC layer of the wireless device from a physical layer of thewireless device. The wireless device may start or restart an LBT failuredetection timer in response to the LBT failure indication, e.g.,reception of the LBT failure indication by the MAC layer from thephysical layer. The wireless device may set the LBT failure indicationcounter to zero (e.g., may reset the LBT failure indication counter)based on the LBT failure detection timer expiring.

In response to the triggering of the consistent LBT failure for theprimary cell, the wireless device may stop the first random accessprocedure, for beam failure recovery, on the primary cell (the first BWPof the primary cell). In an example, stopping the first random accessprocess may comprise resetting counter(s) and/or timer(s) and/orvariable(s) associated with the first random access process. Thewireless device may switch from the first BWP of the primary cell to asecond BWP of the primary cell. In an example, the one or more messagesmay comprise bandwidth part configuration parameters of a plurality ofBWPs, comprising the first BWP and the second BWP, of the primary cell.The bandwidth part configuration parameters of the second BWP of theprimary cell may comprise random access parameters for the second BWP ofthe primary cell, indicating that the second BWP of the primary cell isconfigured with random access occasions/resources. The switching, by thewireless device, from the first BWP of the primary cell to the secondBWP of the primary cell may be based on the second BWP of the primarycell being configured with random access resources/occasion. In anexample, one or more BWPs of the primary cell may be configured withrandom access resources/occasions and the selection of the second BWP,in the one or more BWPs, for switching from the first BWP, may be basedon one or more criteria. The wireless device may initiate a secondrandom access process on the second BWP of the primary cell. Thewireless device may initiate the second random access process in thesecond BWP of primary cell based on the random access parametersconfigured for the second BWP of the primary cell and using the randomaccess occasions/resources configured for the second BWP of the primarycell.

In an example, the second random access process, on the second BWP ofthe primary cell, may be for consistent LBT failure recovery. Thewireless device may initiate a third random access process on the secondBWP of the primary cell, for beam failure recovery, after completion(e.g., successful completion) of the second random access process forconsistent LBT failure recovery. The second random access process, forconsistent LBT failure recovery, may be based on random access processconfiguration parameters. The random access process configurationparameters, used for consistent LBT failure recovery, may be commonlyconfigured for different random access processes not including randomaccess processes performed for beam failure recovery. In an example, therandom access parameters for beam failure recovery may be separatelyconfigured. For example, the first configuration parameters, for beamfailure recovery, may comprise first random access parameters. The oneor more messages, received by the wireless device, may comprise secondrandom access process different from the first random access parameters.The first random access process, for beam failure recovery may be basedon the first random access parameters and the second random accessprocess for consistent LBT failure may be based on the second randomaccess parameters. For example, the first random access parameters, forbeam failure recovery, may indicate random access resources/occasions tobe used for a random access process that is initiated for beam failurerecovery. For example, the first random access parameters, for beamfailure recovery, may indicate a random access response window for beamfailure recovery, a first number of preamble transmissions beforedeclaring a random access failure for beam failure recovery, a powerramping step for a beam failure recovery random access process, aconfiguration index for beam failure recovery, etc. The second randomaccess process, for consistent LBT failure recovery, may comprisetransmitting a transport block (TB), e.g., via a Msg3 message (in afour-step random access process) or a MsgA message (in a two-step randomaccess process). The TB may comprise an LBT failure MAC CE. The LBTfailure MAC CE may have one of a short format (one octet) and longformat (four octets) depending on highest ServingCellIndex of theserving cells configured for the wireless device (e.g., the one-octetformat when the highest ServingCellIndex is less than eight and thefour-octet format otherwise). The LBT failure MAC CE may indicate forwhich serving cell(s) the consistent LBT failure is triggered. Thewireless device may multiplex the LBT failure MAC CE with other logicalchannel(s) and/or MAC CE(s) in the TB. The multiplexing of the LBTfailure MAC CE with other logical channel(s) and/or MAC CE(s) may bebased on a logical channel prioritization procedure. The logical channelprioritization procedure may utilize the priorities of logicalchannel(s) and MAC CE(s). For the purpose of the logical channelprioritization procedure, the priority of the LBT failure MAC CE may behigher than the priorities of data from any logical channel exceptuplink common control channel (UL-CCCH) logical channel.

In an example, the second random access process, on the second BWP ofthe primary cell, may be for beam failure recovery. The wireless devicemay initiate a third random access process on the second BWP of theprimary cell, for consistent LBT failure recovery, after completion(e.g., successful completion) of the second random access process forbeam failure recovery. The second random access process, for beamfailure recovery, may be based on random access process configurationparameters configured for beam failure recovery. The second randomaccess process may comprise transmitting a transport block (TB), e.g.,via a Msg3 message (in a four-step random access process) or a MsgAmessage (in a two-step random access process). The TB may comprise abeam failure recovery (BFR) MAC CE. The BFR MAC CE may have one of ashort format (one octet) and long format (four octets) depending onhighest ServingCellIndex of the serving cells configured for thewireless device (e.g., the one-octet format when the highestServingCellIndex is less than eight and the four-octet formatotherwise). The BFR MAC CE may indicate on which serving cell(s) thebeam failure is detected. The wireless device may multiplex the BFR MACCE with other logical channel(s) and/or MAC CE(s) in the TB. Themultiplexing of the BFR MAC CE with other logical channel(s) and/or MACCE(s) may be based on a logical channel prioritization procedure. Thelogical channel prioritization procedure may utilize the priorities oflogical channel(s) and MAC CE(s). For the purpose of the logical channelprioritization procedure, the priority of the BFR MAC CE may be higherthan the priorities of data from any logical channel except uplinkcommon control channel (UL-CCCH) logical channel.

In an example embodiment as shown in FIG. 35, a wireless device mayinitiate a first random access process in a first BWP of a primary cell.The first random access process may be initiated/triggered based on atriggering event such as scheduling request failure (e.g., a schedulingrequest counter reaching a maximum value and receiving no uplink grant),establishing time alignment for a secondary timing advance group (TAG),beam failure recovery, etc. The wireless may trigger consistent LBTfailure for the primary cell. The triggering of the consistent LBTfailure for the primary cell may be based on an LBT failure indicationcounter reaching a first number (e.g., determined based on an RRCconfigured parameter e.g., FailureInstanceMaxCount) as described above.In response to the triggering of the consistent LBT failure for theprimary cell, the wireless device may stop the first random accessprocess. In an example, stopping the first random access process maycomprise resetting counter(s) and/or timer(s) and/or variable(s)associated with the first random access process. The wireless device mayswitch from the first BWP of the primary cell to a second BWP of theprimary cell. In an example, the one or more messages may comprisebandwidth part configuration parameters of a plurality of BWPs,comprising the first BWP and the second BWP, of the primary cell. Thebandwidth part configuration parameters of the second BWP of the primarycell may comprise random access parameters for the second BWP of theprimary cell, indicating that the second BWP of the primary cell isconfigured with random access occasions/resources. The switching, by thewireless device, from the first BWP of the primary cell to the secondBWP of the primary cell may be based on the second BWP of the primarycell being configured with random access resources/occasion. In anexample, one or more BWPs of the primary cell may be configured withrandom access resources/occasions and the selection of the second BWP,in the one or more BWPs, for switching from the first BWP, may be basedon one or more criteria. The wireless device may initiate a secondrandom access process on the second BWP of the primary cell. Thewireless device may initiate the second random access process in thesecond BWP of primary cell based on the random access parametersconfigured for the second BWP of the primary cell and using the randomaccess occasions/resources configured for the second BWP of the primarycell. In an example, the second random access process, on the second BWPof the primary cell, may be for consistent LBT failure recovery.

In an example embodiment as shown in FIG. 36, a wireless device maytrigger consistent LBT failures for a primary cell. The triggering ofthe consistent LBT failure may be based on LBT failure recoveryconfiguration parameters. The triggering of the consistent LBT failuremay be based on failure of LBT procedures for uplink transmissions onthe primary cell. The configuration parameters for LBT failure recoverymay comprise a first parameter (e.g., FailureInstanceMaxCount)indicating a first number of LBT failure instances that triggers LBTfailure recovery. The triggering of the consistent LBT failure may bebased on an LBT failure indication counter reaching the first number. Inan example, the wireless device may increment the LBT failure indicationcounter by one based on an LBT failure indication, for example receptionof the LBT failure indication by a MAC layer of the wireless device froma physical layer of the wireless device. The wireless device may startor restart an LBT failure detection timer in response to the LBT failureindication, e.g., reception of the LBT failure indication by the MAClayer from the physical layer. The wireless device may set the LBTfailure indication counter to zero (e.g., may reset the LBT failureindication counter) based on the LBT failure detection timer expiring.

In response to the triggering of the consistent LBT failure for theprimary cell, the wireless device may initiate a first random access onthe primary cell for consistent LBT failure recovery. The first randomaccess process, for consistent LBT failure recovery, may be based onrandom access process configuration parameters. The random accessprocess configuration parameters, used for consistent LBT failurerecovery, may be commonly configured for different random accessprocesses not including random access processes performed for beamfailure recovery. In an example, the random access parameters for beamfailure recovery may be separately configured.

The wireless device may detect a beam failure on the primary cell of thewireless device. In an example, the detection of the beam failure on theprimary cell may be while the first random access process for theconsistent LBT failure recovery is ongoing. The configuration for beamfailure recovery may comprise a first parameter (e.g.,beamFailurelnstanceMaxCount) indicating a first number of beam failureinstances that triggers beam failure recovery. The detection of the beamfailure may be based on a beam failure instance indication counterreaching the first number. In an example, the wireless device mayincrement the beam failure instance indication counter by one based on abeam failure indication, for example reception of the beam failureindication by a MAC layer of the wireless device from a physical layerof the wireless device. The wireless device may start or restart a beamfailure detection timer in response to the beam failure indication,e.g., reception of the beam failure indication by the MAC layer from thephysical layer. The wireless device may set the beam failure instanceindication counter to zero (e.g., reset the beam failure instanceindication counter) based on the beam failure detection timer expiring.

Based on the detection of the beam failure, the wireless device may stopthe first random access process for consistent LBT failure. In anexample, stopping the first random access process may comprise resettingcounter(s) and/or timer(s) and/or variable(s) associated with the firstrandom access process. The wireless device may initiate a second randomaccess process on the primary cell for beam failure recovery. Thewireless device may initiate/perform the second random access processbased on random access process configuration parameters configured forbeam failure recovery. The configuration parameters for beam failurerecovery may comprise random access parameters configured for beamfailure recovery. The random access parameters for beam failure recoverymay indicate random access resources/occasions to be used for a randomaccess process that is initiated for beam failure recovery. For example,the random access parameters for beam failure recovery may indicate arandom access response window for beam failure recovery, a first numberof preamble transmissions before declaring a random access failure forbeam failure recovery, a power ramping step for a beam failure recoveryrandom access process, a configuration index for beam failure recovery,etc. The second random access process may comprise transmitting atransport block (TB), e.g., via a Msg3 message (in a four-step randomaccess process) or a MsgA message (in a two-step random access process).The TB may comprise a beam failure recovery (BFR) MAC CE. The BFR MAC CEmay have one of a short format (one octet) and long format (four octets)depending on highest ServingCellIndex of the serving cells configuredfor the wireless device (e.g., the one-octet format when the highestServingCellIndex is less than eight and the four-octet formatotherwise). The BFR MAC CE may indicate on which serving cell(s) thebeam failure is detected. The wireless device may multiplex the BFR MACCE with other logical channel(s) and/or MAC CE(s) in the TB. Themultiplexing of the BFR MAC CE with other logical channel(s) and/or MACCE(s) may be based on a logical channel prioritization procedure. Thelogical channel prioritization procedure may utilize the priorities oflogical channel(s) and MAC CE(s). For the purpose of the logical channelprioritization procedure, the priority of the BFR MAC CE may be higherthan the priorities of data from any logical channel except uplinkcommon control channel (UL-CCCH) logical channel.

In an example, the wireless device may initiate a third random accessprocess for the consistent LBT failure recovery after the second randomaccess process is completed (e.g., successfully completed). The thirdrandom access process, for consistent LBT failure recovery, may comprisetransmitting a transport block (TB), e.g., via a Msg3 message (in afour-step random access process) or a MsgA message (in a two-step randomaccess process). The TB may comprise an LBT failure MAC CE. The LBTfailure MAC CE may have one of a short format (one octet) and longformat (four octets) depending on highest ServingCellIndex of theserving cells configured for the wireless device (e.g., the one-octetformat when the highest ServingCellIndex is less than eight and thefour-octet format otherwise). The LBT failure MAC CE may indicate forwhich serving cell(s) the consistent LBT failure is triggered. Thewireless device may multiplex the LBT failure MAC CE with other logicalchannel(s) and/or MAC CE(s) in the TB. The multiplexing of the LBTfailure MAC CE with other logical channel(s) and/or MAC CE(s) may bebased on a logical channel prioritization procedure. The logical channelprioritization procedure may utilize the priorities of logicalchannel(s) and MAC CE(s). For the purpose of the logical channelprioritization procedure, the priority of the LBT failure MAC CE may behigher than the priorities of data from any logical channel exceptuplink common control channel (UL-CCCH) logical channel.

In an example embodiment as shown in FIG. 37, the wireless device mayinitiate a first random access process on the primary cell in responseto triggering consistent LBT failure for the primary cell. Thetriggering the consistent LBT failure for the primary cell may be basedon the LBT failure recovery configuration parameters and based on an LBTfailure instance indication counter reaching a first number (e.g., asindicated by the LBT failure recovery configuration parameters such as aFailureInstanceMaxCount parameter). The wireless device may detect beamfailure for the primary cell, e.g., while the first random accessprocess for consistent LBT failure recovery is ongoing. The wirelessdevice may detect the beam failure for the primary cell based on theconfiguration parameters for beam failure recovery and/or radio linkmonitoring. In response to the detecting the beam failure, the wirelessdevice may continue the first random access process, for the consistentLBT failure recovery, and may initiate a second random access process,for beam failure recovery after the first random access process beingcompleted (e.g., being successfully completed).

In an example embodiment as shown in FIG. 38, the wireless device mayinitiate a first random access process on the primary cell in responseto detecting beam failure for the primary cell. The triggering the beamfailure recovery for the primary cell may be based on the beam failurerecovery configuration parameters and based on a beam failure indicationcounter reaching a first number (e.g., as indicated by the beam failurerecovery configuration parameters such as a beamFailurelnstanceMaxCountparameter). The wireless device may trigger consistent failure for theprimary cell, e.g., while the first random access process for beamfailure recovery is ongoing. The wireless device may trigger theconsistent LBT failure for the primary cell based on the configurationparameters for LBT failure recovery. In response to the triggering theconsistent LBT failure, the wireless device may continue the firstrandom access process, for the consistent LBT failure recovery, and mayinitiate a second random access process, for beam failure recovery afterthe first random access process being completed (e.g., beingsuccessfully completed). In an example, the wireless device may switchfrom a first BWP of the primary cell (e.g., the active BWP of theprimary cell on which the first random access process, for beam failurerecovery, is initiated and for which the consistent LBT failure istriggered) to a second BWP of the primary cell based on the first randomaccess process for beam failure recovery being successfully completed.

In an example embodiment as shown in FIG. 39, the wireless device mayinitiate a first random access process on the primary cell in responseto detecting beam failure for the primary cell and for beam failurerecovery. The triggering the beam failure recovery for the primary cellmay be based on the beam failure recovery configuration parameters andbased on a beam failure indication counter reaching a first number(e.g., as indicated by the beam failure recovery configurationparameters such as a beamFailurelnstanceMaxCount parameter). Thewireless device may trigger consistent failure for the primary cell,e.g., while the first random access process, for beam failure recovery,is ongoing. The wireless device may trigger the consistent LBT failurefor the primary cell based on the configuration parameters for LBTfailure recovery. In response to the triggering the consistent LBTfailure, the wireless device may continue or stop the first randomaccess process, for the consistent LBT failure recovery based on a stageof the first random access process for beam failure recovery, forexample based on whether random access resources are selected and/orbased on whether a random access message (e.g., a MsgA in a two-steprandom access process; or a Msg1/preamble or a Msg3 in a four-steprandom access process) is transmitted or based on a random accessmessage (e.g., a MsgB in a two-step random access process; or a Msg2/RARor Msg4 in a four-step random access process) is received.

In accordance with various exemplary embodiments in the presentdisclosure, a device (e.g., a wireless device, a base station and/oralike) may include one or more processors and may include memory thatmay store instructions. The instructions, when executed by the one ormore processors, cause the device to perform actions as illustrated inthe accompanying drawings and described in the specification. The orderof events or actions, as shown in a flow chart of this disclosure, mayoccur and/or may be performed in any logically coherent order. In someexamples, at least two of the events or actions shown may occur or maybe performed at least in part simultaneously and/or in parallel. In someexamples, one or more additional events or actions may occur or may beperformed prior to, after, or in between the events or actions shown inthe flow charts of the present disclosure.

FIG. 40 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 4010, a wirelessdevice may receive one or more messages comprising: first configurationparameters for beam failure recovery; and second configurationparameters for listen-before-talk (LBT) failure recovery. At 4020, thewireless device may initiate, based on the first configurationparameters and in response to detecting a beam failure on a primarycell, a first random access process on a first bandwidth part (BWP) ofthe primary cell for beam failure recovery. At 4030, the wireless devicemay trigger, based on the second configuration parameters, consistentLBT failure for the primary cell. At 4040, the wireless device may stopthe first random access process, for the beam failure recovery, based onthe triggering the consistent LBT failure. At 4050, the wireless devicemay switch from the first BWP of the primary cell to a second BWP of theprimary cell as an active BWP of the primary cell. At 4060, the wirelessdevice may initiate a second random access process on the second BWP ofthe primary cell.

In an example embodiment, the second random access process, initiated at4060, may be for consistent LBT failure recovery. In an exampleembodiment, the wireless device may initiate a third random accessprocess, for the beam failure recovery, after the second random accessprocess is successfully completed. In an example, embodiment, the secondrandom access process, initiated at 4060, may comprise transmitting atransport block comprising an LBT failure medium access control (MAC)control element (CE). In an example embodiment, the transmitting thetransport block may be based on a logical channel prioritizationprocedure. A first priority associated with the LBT failure MAC CE maybe higher than a second priority associated with data from any logicalchannel except uplink common control channel (UL-CCCH) logical channel.

In an example embodiment, the second random access process, initiated at4060, may be for the beam failure recovery. In an example embodiment,the wireless device may initiate a third random access process forconsistent LBT failure recovery after the second random access processis successfully completed. In an example embodiment, the second randomaccess process, initiated at 4060, may comprise transmitting a transportblock comprising a beam failure recovery medium access control (MAC)control element (CE). In an example embodiment, the transmitting thetransport block may be based on a logical channel prioritizationprocedure. A first priority associated with the beam failure recoveryMAC CE may be higher than a second priority associated with data fromany logical channel except uplink common control channel (UL-CCCH)logical channel.

In an example embodiment, the first configuration parameters, receivedat 4010 for beam failure recovery, may comprise first random accessparameters. The one or more messages, received at 4010, may furthercomprise second random access parameters. The first random accessprocess, initiated at 4020 for the beam failure recovery, may be basedon the first random access parameters. The second random access process,initiated at 4060, may be for consistent LBT failure recovery and may bebased on the second random access parameters. In an example embodiment,the first random access parameters may indicate random access resourcesfor a beam failure recovery random access process. In an exampleembodiment, the first random access parameters may indicate: a randomaccess response window for beam failure recovery; a first number ofpreamble transmissions before declaring a random access failure for beamfailure recovery; a power ramping step for a beam failure recoveryrandom access process; and a configuration index for beam failurerecovery.

In an example embodiment, the first configuration parameters, receivedat 4010 for beam failure recovery, may comprise an identifier of asearch space for monitoring a control channel in a beam failure recoveryrandom access process.

In an example embodiment, the first configuration parameters, receivedat 4010, may comprise a first parameter indicating a first number ofbeam failure instances that triggers beam failure recovery. Thedetecting the beam failure may be based on a beam failure instanceindication counter reaching the first number. In an example embodiment,the detecting the beam failure at 4020 may comprise incrementing thebeam failure instance indication counter by one based on a beam failureindication. In an example embodiment, the detecting the beam failure at4020 may comprise setting the beam failure instance indication counterto zero based on a beam failure detection timer expiring.

In an example embodiment, the second configuration parameters, receivedat 4010, may comprise a first parameter indicating a first number of LBTfailure instances that triggers LBT failure recovery. The triggering theconsistent LBT failure, at 4030, may be based on an LBT failureindication counter reaching the first number. In an example embodiment,the triggering the consistent LBT failure, at 4030, may compriseincrementing the LBT failure indication counter by one based on an LBTfailure indication. In an example embodiment, triggering the consistentLBT failure at 4030 may comprise setting the LBT failure indicationcounter to zero based on an LBT failure detection timer expiring.

In an example embodiment, the second BWP of the primary cell, on whichthe second random access process is initiated at 4060, may be configuredwith random access occasions. The switching, at 4050, from the first BWPof the primary cell to a second BWP of the primary cell may be based onthe second BWP of the primary cell being configured with the randomaccess occasions.

FIG. 41 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 4110, a wirelessdevice may initiate a first random access process on a first bandwidthpart (BWP) of a primary cell for beam failure recovery. At 4120, thewireless device may trigger consistent listen-before-talk (LBT) failurefor the primary cell. At 4130, the wireless device may stop the firstrandom access process based on the triggering the consistent LBTfailure. At 4140, the wireless device may switch from the first BWP ofthe primary cell to a second BWP of the primary cell as an active BWP ofthe primary cell. At 4150, the wireless device may initiate a secondrandom access process on the second BWP of the primary cell.

FIG. 42 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 4210, a wirelessdevice may initiate a first random access process on a first bandwidthpart (BWP) of a primary cell. At 4220, the wireless device may triggerconsistent listen-before-talk (LBT) failure for the primary cell. At4230, the wireless device may stop the first random access process basedon the triggering the consistent LBT failure. At 4240, the wirelessdevice may switch from the first BWP of the primary cell to a second BWPof the primary cell as an active BWP of the primary cell. At 4250, thewireless device may initiate a second random access process on thesecond BWP of the primary cell.

In an example embodiment, the second random access process, initiated at4250, may be for consistent LBT failure recovery.

FIG. 43 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 4310, a wirelessdevice may receive one or more messages comprising: first configurationparameters for listen-before-talk (LBT) failure recovery; and secondconfiguration parameters for beam failure recovery. At 4320, thewireless device may trigger consistent LBT failure for a primary cellbased on the first configuration parameters. At 4330, the wirelessdevice may initiate, in response to the triggering the consistent LBTfailure, a first random access process on the primary cell forconsistent LBT failure recovery. At 4340, the wireless device maydetect, based on the second configuration parameters, a beam failure forthe primary cell. At 4350, the wireless device may stop the first randomaccess process, for the consistent LBT failure recovery, based on thedetecting the beam failure. At 4360, the wireless device may initiate asecond random access process on the primary cell for beam failurerecovery.

In an example embodiment, the wireless device may initiate a thirdrandom access process for the consistent LBT failure recovery after thesecond random access process, initiated at 4360, is successfullycompleted. In an example embodiment, the third random access process maycomprise transmitting a transport block comprising an LBT failure mediumaccess control (MAC) control element (CE). In an example embodiment, thetransmitting the transport block may be based on a logical channelprioritization procedure. A first priority associated with the LBTfailure recovery MAC CE may be higher than a second priority associatedwith data from any logical channel except uplink common control channel(UL-CCCH) logical channel.

In an example embodiment, the second random access process, initiated at4360, may comprise transmitting a transport block comprising a beamfailure recovery medium access control (MAC) control element (CE). In anexample embodiment, the transmitting the transport block may be based ona logical channel prioritization procedure. A first priority associatedwith the beam failure recovery MAC CE may be higher than a secondpriority associated with data from any logical channel except uplinkcommon control channel (UL-CCCH) logical channel.

In an example embodiment, the second configuration parameters, receivedat 4310 for beam failure recovery, may comprise first random accessparameters. The one or more messages, received at 4310, may furthercomprise second random access parameters. The first random accessprocess, initiated at 4330 for the LBT failure recovery, may be based onthe second random access parameters. The second random access process,initiated at 4360 for the beam failure recovery, may be based on thefirst random access parameters. In an example embodiment, the firstrandom access parameters may indicate random access resources for a beamfailure recovery random access process. In an example embodiment, thefirst random access parameters may indicate: a random access responsewindow for beam failure recovery; a first number of preambletransmissions before declaring a random access failure for beam failurerecovery; a power ramping step for a beam failure recovery random accessprocess; and a configuration index for beam failure recovery.

In an example embodiment, the second configuration parameters, receivedat 4310 for beam failure recovery, may comprise an identifier of asearch space for monitoring a control channel in a beam failure recoveryrandom access process.

In an example embodiment, the second configuration parameters, receivedat 4310, may comprise a first parameter indicating a first number ofbeam failure instances that triggers beam failure recovery. Thedetecting the beam failure, at 4340, may be based on a beam failureinstance indication counter reaching the first number. In an exampleembodiment, the detecting the beam failure, at 4340, may compriseincrementing the beam failure instance indication counter by one basedon a beam failure indication. In an example embodiment, the detectingthe beam failure, at 4340, may comprise setting the beam failureinstance indication counter to zero based on a beam failure detectiontimer expiring.

In an example embodiment, the first configuration parameters, receivedat 4310, may comprise a first parameter indicating a first number of LBTfailure instances that triggers LBT failure recovery. The triggering theconsistent LBT failure, at 4320, may be based on an LBT failureindication counter reaching the first number. In an example embodiment,the triggering the consistent LBT failure, at 4320, may compriseincrementing the LBT failure indication counter by one based on an LBTfailure indication. In an example embodiment, the triggering theconsistent LBT failure, at 4320, may comprise setting the LBT failureindication counter to zero based on an LBT failure detection timerexpiring.

FIG. 44 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 4410, a wirelessdevice may receive may initiate, in response to triggering consistentlisten-before-talk (LBT) failure for a primary cell, a first randomaccess process on the primary cell for consistent LBT failure recovery.At 4420, the wireless device may detect a beam failure for the primarycell. At 4430, the wireless device may stop the first random accessprocess, for the consistent LBT failure recovery, based on the detectingthe beam failure. At 4440, the wireless device may initiate a secondrandom access process on the primary cell for beam failure recovery.

FIG. 45 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 4510, a wirelessdevice may initiate, in response to triggering consistent listen-before(LBT) failure for a primary cell, a first random access process on theprimary cell for consistent LBT failure recovery. At 4520, the wirelessdevice may detect a beam failure for the primary cell. At 4530, based onthe detecting the beam failure: the wireless device may continue thefirst random access process; and the wireless device may initiate asecond random access process on the primary cell for beam failurerecovery based on the first random access process being successfullycompleted.

In an example embodiment, the detecting the beam failure at 4520 may bewhile the first random access process is ongoing.

FIG. 46 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 4610, a wirelessdevice may initiate, in response to detecting beam failure for a primarycell, a first random access process on the primary cell for beam failurerecovery. At 4620, the wireless device may trigger a consistentlisten-before-talk (LBT) failure for the primary cell. At 4630, based onthe triggering the consistent LBT failure: the wireless device maycontinue the first random access process; and the wireless device mayinitiate a second random access process on the primary cell forconsistent LBT failure recovery based on the first random access processbeing successfully completed.

In an example embodiment, the wireless device may switch from a firstbandwidth part (BWP) of the primary cell to a second BWP of the primarycell based on the first random access process being successfullycompleted.

FIG. 47 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 4710, a wirelessdevice may initiate, in response to detecting beam failure for a primarycell, a first random access process on the primary cell for beam failurerecovery. At 4720, the wireless device may trigger a consistentlisten-before-talk (LBT) failure for the primary cell. At 4730, thewireless device may stop or continue the first random access process,for beam failure recovery, based on a stage of the first random accessprocess.

In an example embodiment, the wireless device may initiate a secondrandom access process on the primary cell for consistent LBT failurerecovery.

In an example embodiment, wherein the stopping or the continuing thefirst random access process, at 4730, may be based on whether a randomaccess message is transmitted. In an example embodiment, the randomaccess message may be one of a Msg1 message or a Msg3 message. In anexample embodiment, the random access message may be a MsgA message.

In an example embodiment, the stopping or the continuing the firstrandom access process may be based on whether a random access message isreceived. In an example embodiment, the random access message may be oneof a Msg2 or a Msg4 message. In an example embodiment, the random accessmessage may be a MsgB message.

Various exemplary embodiments of the disclosed technology are presentedas example implementations and/or practices of the disclosed technology.The exemplary embodiments disclosed herein are not intended to limit thescope. Persons of ordinary skill in the art will appreciate that variouschanges can be made to the disclosed embodiments without departure fromthe scope. After studying the exemplary embodiments of the disclosedtechnology, alternative aspects, features and/or embodiments will becomeapparent to one of ordinary skill in the art. Without departing from thescope, various elements or features from the exemplary embodiments maybe combined to create additional embodiments. The exemplary embodimentsare described with reference to the drawings. The figures and theflowcharts that demonstrate the benefits and/or functions of variousaspects of the disclosed technology are presented for illustrationpurposes only. The disclosed technology can be flexibly configuredand/or reconfigured such that one or more elements of the disclosedembodiments may be employed in alternative ways. For example, an elementmay be optionally used in some embodiments or the order of actionslisted in a flowchart may be changed without departure from the scope.

An example embodiment of the disclosed technology may be configured tobe performed when deemed necessary, for example, based on one or moreconditions in a wireless device, a base station, a radio and/or corenetwork configuration, a combination thereof and/or alike. For example,an example embodiment may be performed when the one or more conditionsare met. Example one or more conditions may be one or moreconfigurations of the wireless device and/or base station, traffic loadand/or type, service type, battery power, a combination of thereofand/or alike. In some scenarios and based on the one or more conditions,one or more features of an example embodiment may be implementedselectively.

In this disclosure, the articles “a” and “an” used before a group of oneor more words are to be understood as “at least one” or “one or more” ofwhat the group of the one or more words indicate. The use of the term“may” before a phrase is to be understood as indicating that the phraseis an example of one of a plurality of useful alternatives that may beemployed in an embodiment in this disclosure.

In this disclosure, an element may be described using the terms“comprises”, “includes” or “consists of” in combination with a list ofone or more components. Using the terms “comprises” or “includes”indicates that the one or more components are not an exhaustive list forthe description of the element and do not exclude components other thanthe one or more components. Using the term “consists of” indicates thatthe one or more components is a complete list for description of theelement. In this disclosure, the term “based on” is intended to mean“based at least in part on”. The term “based on” is not intended to mean“based only on”. In this disclosure, the term “and/or” used in a list ofelements indicates any possible combination of the listed elements. Forexample, “X, Y, and/or Z” indicates X; Y; Z; X and Y; X and Z; Y and Z;or X, Y, and Z.

Some elements in this disclosure may be described by using the term“may” in combination with a plurality of features. For brevity and easeof description, this disclosure may not include all possiblepermutations of the plurality of features. By using the term “may” incombination with the plurality of features, it is to be understood thatall permutations of the plurality of features are being disclosed. Forexample, by using the term “may” for description of an element with fourpossible features, the element is being described for all fifteenpermutations of the four possible features. The fifteen permutationsinclude one permutation with all four possible features, fourpermutations with any three features of the four possible features, sixpermutations with any two features of the four possible features andfour permutations with any one feature of the four possible features.

Although mathematically a set may be an empty set, the term set used inthis disclosure is a nonempty set. Set B is a subset of set A if everyelement of set B is in set A. Although mathematically a set has an emptysubset, a subset of a set is to be interpreted as a non-empty subset inthis disclosure. For example, for set A={subcarrier1, subcarrier2}, thesubsets are {subcarrier1}, {subcarrier2} and {subcarrier1, subcarrier2}.

In this disclosure, the phrase “based on” may be used equally with“based at least on” and what follows “based on” or “based at least on”indicates an example of one of plurality of useful alternatives that maybe used in an embodiment in this disclosure. The phrase “in response to”may be used equally with “in response at least to” and what follows “inresponse to” or “in response at least to” indicates an example of one ofplurality of useful alternatives that may be used in an embodiment inthis disclosure. The phrase “depending on” may be used equally with“depending at least on” and what follows “depending on” or “depending atleast on” indicates an example of one of plurality of usefulalternatives that may be used in an embodiment in this disclosure. Thephrases “employing” and “using” and “employing at least” and “using atleast” may be used equally in this in this disclosure and what follows“employing” or “using” or “employing at least” or “using at least”indicates an example of one of plurality of useful alternatives that maybe used in an embodiment in this disclosure.

The example embodiments disclosed in this disclosure may be implementedusing a modular architecture comprising a plurality of modules. A modulemay be defined in terms of one or more functions and may be connected toone or more other elements and/or modules. A module may be implementedin hardware, software, firmware, one or more biological elements (e.g.,an organic computing device and/or a neurocomputer) and/or a combinationthereof and/or alike. Example implementations of a module may be assoftware code configured to be executed by hardware and/or a modelingand simulation program that may be coupled with hardware. In an example,a module may be implemented using general-purpose or special-purposeprocessors, digital signal processors (DSPs), microprocessors,microcontrollers, application-specific integrated circuits (ASICs),programmable logic devices (PLDs) and/or alike. The hardware may beprogrammed using machine language, assembly language, high-levellanguage (e.g., Python, FORTRAN, C, C++ or the like) and/or alike. In anexample, the function of a module may be achieved by using a combinationof the mentioned implementation methods.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, one or more messages comprising: first configuration parametersfor beam failure recovery, comprising first random access parameters;second configuration parameters for listen-before-talk (LBT) failurerecovery; and second random access parameters; initiating, based on thefirst configuration parameters and in response to detecting a beamfailure on a primary cell, a first random access process on a firstbandwidth part (BWP) of the primary cell for beam failure recovery basedon the first random access parameters; triggering, based on the secondconfiguration parameters, consistent LBT failure for the primary cell;stopping the first random access process, for the beam failure recovery,based on the triggering the consistent LBT failure; switching from thefirst BWP of the primary cell to a second BWP of the primary cell as anactive BWP of the primary cell; and initiating a second random accessprocess on the second BWP of the primary cell for consistent LBT failurerecovery and based on the second random access parameters.
 2. The methodof claim 1, wherein the second random access process, for consistent LBTfailure recovery, is one of a two-step random access process and afour-step random access process.
 3. The method of claim 2, furthercomprising initiating a third random access process, for the beamfailure recovery, after the second random access process is successfullycompleted.
 4. The method of claim 2, wherein the second random accessprocess comprises transmitting a transport block comprising an LBTfailure medium access control (MAC) control element (CE).
 5. The methodof claim 4, wherein: the transmitting the transport block is based on alogical channel prioritization procedure; and a first priorityassociated with the LBT failure MAC CE is higher than a second priorityassociated with data from any logical channel except uplink commoncontrol channel (UL-CCCH) logical channel.
 6. The method of claim 1,wherein the first random access process, for the beam failure recovery,is one of a two-step random access process and a four-step random accessprocess.
 7. The method of claim 6, further comprising initiating a thirdrandom access process for beam failure recovery after the second randomaccess process is successfully completed.
 8. The method of claim 7,wherein the third random access process comprises transmitting atransport block comprising a beam failure recovery medium access control(MAC) control element (CE).
 9. The method of claim 8, wherein: thetransmitting the transport block is based on a logical channelprioritization procedure; and a first priority associated with the beamfailure recovery MAC CE is higher than a second priority associated withdata from any logical channel except uplink common control channel(UL-CCCH) logical channel.
 10. The method of claim 1, wherein the firstrandom access parameters indicate random access resources for a beamfailure recovery random access process.
 11. The method of claim 1,wherein the first random access parameters indicate: a random accessresponse window for beam failure recovery; a first number of preambletransmissions before declaring a random access failure for beam failurerecovery; a power ramping step for a beam failure recovery random accessprocess; and a configuration index for beam failure recovery.
 12. Themethod of claim 1, wherein the first configuration parameters for beamfailure recovery comprise an identifier of a search space for monitoringa control channel in a beam failure recovery random access process. 13.The method of claim 1, wherein: the first configuration parameterscomprise a first parameter indicating a first number of beam failureinstances that triggers beam failure recovery; and the detecting thebeam failure is based on a beam failure instance indication counterreaching the first number.
 14. The method of claim 13, wherein thedetecting the beam failure comprises incrementing the beam failureinstance indication counter by one based on a beam failure indication.15. The method of claim 13, wherein the detecting the beam failurecomprises setting the beam failure instance indication counter to zerobased on a beam failure detection timer expiring.
 16. The method ofclaim 1, wherein: the second configuration parameters comprise a firstparameter indicating a first number of LBT failure instances thattriggers LBT failure recovery; and the triggering the consistent LBTfailure is based on an LBT failure indication counter reaching the firstnumber.
 17. The method of claim 16, wherein the triggering theconsistent LBT failure comprises incrementing the LBT failure indicationcounter by one based on an LBT failure indication.
 18. The method ofclaim 16, wherein the triggering the consistent LBT failure comprisessetting the LBT failure indication counter to zero based on an LBTfailure detection timer expiring.
 19. The method of claim 1, wherein:the second BWP of the primary cell is configured with random accessoccasions; and the switching from the first BWP of the primary cell to asecond BWP of the primary cell is based on the second BWP of the primarycell being configured with the random access occasions.